Systems and methods of transmitting and storing data based on connection for a vehicle

ABSTRACT

A system for transmitting and storing data based on a connection for a vehicle is presented. The system includes a computing device, the computing device configured to receive a vehicle data, communicatively connect the computing device to a second device as a function of a mesh network, authenticate a second device as a function of an authentication module, generate a vehicle collection datum as a function of the vehicle data, communicate the vehicle collection datum to the second device as a function of the mesh network, and store the vehicle collection datum in a recorder database as a function of a lack of identification of the mesh network.

FIELD OF THE INVENTION

The present invention generally relates to the field of data transmission. In particular, the present invention is directed to systems and methods for transmitting and storing data based on a connection for a vehicle.

BACKGROUND

Vehicles collect vast amounts of valuable data during operation. Vehicle data may be used to analyze trends, patterns, efficiency metrics, and the like. Vehicles operating in the air such as aircrafts collect data to determine other relevant metrics. Analysis may require a large amount of computing power and in some cases is based on aircraft data from multiple aircrafts. In some instances, weight or connectivity limitations prevent the analysis from occurring onboard the aircraft. Moreover, the volatility of reliable connection may pose greater risk to the safe transfer of valuable information through a volatile network. An aircraft lost in flight may be due to an emergency of electrical systems of the aircraft which may degrade aircraft data collected but also pose risk in retrieving aircraft data collected by the aircraft depending on the location of the aircraft.

SUMMARY OF THE DISCLOSURE

In an aspect a system for transmitting and storing data based on a connection for a vehicle is presented. The system includes a computing device, the computing device configured to receive a vehicle data, communicatively connect the computing device to a second device as a function of a mesh network, authenticate a second device as a function of an authentication module, generate a vehicle collection datum as a function of the vehicle data, communicate the vehicle collection datum to the second device as a function of the mesh network, and store the vehicle collection datum in a recorder database as a function of a lack of identification of the mesh network.

In another aspect, a method for transmitting and storing data based on a connection for a vehicle is presented. The method includes receiving, by a computing device, a vehicle data, communicatively connecting the computing device to a second device as a function of a mesh network, authenticating a second device as a function of an authentication module, generating a vehicle collection datum as a function of the vehicle data, communicating the vehicle collection datum to the second device as a function of the mesh network, and storing the vehicle collection datum in a recorder database as a function of a lack of identification of the mesh network.

These and other aspects and features of non-limiting embodiments of the present invention will become apparent to those skilled in the art upon review of the following description of specific non-limiting embodiments of the invention in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

For the purpose of illustrating the invention, the drawings show aspects of one or more embodiments of the invention. However, it should be understood that the present invention is not limited to the precise arrangements and instrumentalities shown in the drawings, wherein:

FIG. 1 is a block diagram of an exemplary embodiment of a system for transmitting and storing data based on connection for a vehicle;

FIG. 2 is a block diagram of an exemplary embodiment of a system for a mesh network for a vehicle;

FIG. 3 is a block diagram illustrating an exemplary embodiment of a recorder database;

FIG. 4 is a block diagram of an exemplary embodiment of an authentication module;

FIG. 5 is a block diagram illustrating an exemplary embodiment of an authentication database;

FIG. 6 is a block diagram illustrating an exemplary embodiment of a biometric database;

FIG. 7 is a block diagram of an exemplary embodiment of an avionic mesh network;

FIG. 8 is a flow diagram of an exemplary method for transmitting and storing data based on connection for a vehicle;

FIG. 9 is an illustration of an exemplary embodiment of an electric aircraft;

FIG. 10 is a block diagram of an exemplary flight controller;

FIG. 11 is a block diagram of an exemplary machine-learning process; and

FIG. 12 is a block diagram of a computing system that can be used to implement any one or more of the methodologies disclosed herein and any one or more portions thereof.

The drawings are not necessarily to scale and may be illustrated by phantom lines, diagrammatic representations and fragmentary views. In certain instances, details that are not necessary for an understanding of the embodiments or that render other details difficult to perceive may have been omitted.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, that the present invention may be practiced without these specific details. As used herein, the word “exemplary” or “illustrative” means “serving as an example, instance, or illustration.” Any implementation described herein as “exemplary” or “illustrative” is not necessarily to be construed as preferred or advantageous over other implementations. All of the implementations described below are exemplary implementations provided to enable persons skilled in the art to make or use the embodiments of the disclosure and are not intended to limit the scope of the disclosure, which is defined by the claims. For purposes of description herein, the terms “upper”, “lower”, “left”, “rear”, “right”, “front”, “vertical”, “horizontal”, and derivatives thereof shall relate to embodiments oriented as shown for exemplary purposes in FIG. 6 . Furthermore, there is no intention to be bound by any expressed or implied theory presented in the preceding technical field, background, brief summary or the following detailed description. It is also to be understood that the specific devices and processes illustrated in the attached drawings, and described in the following specification, are simply embodiments of the inventive concepts defined in the appended claims. Hence, specific dimensions and other physical characteristics relating to the embodiments disclosed herein are not to be considered as limiting, unless the claims expressly state otherwise.

In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, that the present invention may be practiced without these specific details. As used herein, the word “exemplary” or “illustrative” means “serving as an example, instance, or illustration.” Any implementation described herein as “exemplary” or “illustrative” is not necessarily to be construed as preferred or advantageous over other implementations. All of the implementations described below are exemplary implementations provided to enable persons skilled in the art to make or use the embodiments of the disclosure and are not intended to limit the scope of the disclosure, which is defined by the claims. Furthermore, there is no intention to be bound by any expressed or implied theory presented in the preceding technical field, background, brief summary or the following detailed description. It is also to be understood that the specific devices and processes illustrated in the attached drawings, and described in the following specification, are simply embodiments of the inventive concepts defined in the appended claims. Hence, specific dimensions and other physical characteristics relating to the embodiments disclosed herein are not to be considered as limiting, unless the claims expressly state otherwise.

At a high level, aspects of the present disclosure are directed to systems and methods for vehicle data recording and transmitting. In an embodiment, aspects of the present disclosure can be used to store data when isolated or unable to connect to a network or another device and transmit data when a connection is formed. Aspects of the present disclosure can be used verify a plurality of computing devices and other vehicles within a network and send data once a second device is authenticated. Aspects of the present disclosure can be used to generate a sparse set of vehicle data to compartmentalize a plurality of dynamically received vehicle data to be stored in the event a connection with a network or other device is lost in order to store a reasonably organized set of data that may be compromised by a disconnection during a data transmission.

Aspects of the present disclosure can be used to for any vehicle during operation. Aspects of the present disclosure can also be used for an electric aircraft such as an electric vertical take-off and landing (eVTOL) aircraft and during its flight. This is so, at least in part, because an aircraft during flight may experience a malfunction within its many computing systems in which vehicle data may be lost or compromised in the middle of a data transmission. Additionally, the data can be stored in an encrypted database and/or black box that may contain valuable data regarding the aircraft and its operating status. Moreover, an aircraft experiencing a malfunction in mid-flight may be subject to an emergency landing or crash landing in a remote or unidentified location in which organized vehicle data may be crucial in retrieving.

Aspects of the present disclosure allow for a variety of vehicle data analysis. Vehicle data may be utilized by pilots/drivers or a vehicle company to survey usage patterns, determine ways to improve trips, or perform other analysis. In some instances, vehicle data analysis cannot be performed onboard a vehicle due to computing requirements or weight constraints. Vehicle data from multiple vehicles may be desired, requiring a means of data congregation. However, vehicles traveling in remote areas without a WiFi or cellular connection may experience difficulties in communicating vehicle data to another vehicle or to a shared network. In the disclosed method, a check is performed to determine whether an internet connection is available, and data management is based upon the determination. For example, vehicle data may be relayed in real-time in the event an internet connection is available during a trip. In the event an internet connection is not available during the trip, vehicle data is maintained until a connection is available. Data for multiple vehicles may be sent to a shared network and analyzed, with the resulting analysis provided to relevant parties.

Aspects of the present disclosure can be used to generate a lower resolution data or subset of data recorded by the recording device which may be desired in certain analysis. Aspects of the present disclosure may be executed on a second device either installed on the vehicle or independent of the vehicle, wherein a subset of vehicle data recording device data is transferred and stored on the second device. For example, a portable device capable of being transported independently of the vehicle such as a smart phone, tablet, smart watch, or other internet of things (IoT) device may be used. A portable device may be ideal in the event the vehicle is not easily transported to a location with an internet connection (e.g. the vehicle is an aircraft that typically lands on water, or a large truck designed for specific terrain). Aspects of the present disclosure may be executed by an application capable of running on multiple platforms.

Referring now to FIG. 1 , a block diagram of an exemplary embodiment of a system 100 for transmitting and storing data based on a connection for a vehicle is presented. Vehicle may include an aircraft. Vehicle may include an electric aircraft. System 100 includes a computing device. Computing device 112 may include a flight controller. computing device 112 may include any computing device as described in this disclosure, including without limitation a microcontroller, microprocessor, digital signal processor (DSP) and/or system on a chip (SoC) as described in this disclosure. Computing device may include, be included in, and/or communicate with a mobile device such as a mobile telephone or smartphone. computing device 112 may include a single computing device operating independently, or may include two or more computing device operating in concert, in parallel, sequentially or the like; two or more computing devices may be included together in a single computing device or in two or more computing devices. computing device 112 may interface or communicate with one or more additional devices as described below in further detail via a network interface device. Network interface device may be utilized for connecting computing device 112 to one or more of a variety of networks, and one or more devices. Examples of a network interface device include, but are not limited to, a network interface card (e.g., a mobile network interface card, a LAN card), a modem, and any combination thereof. Examples of a network include, but are not limited to, a wide area network (e.g., the Internet, an enterprise network), a local area network (e.g., a network associated with an office, a building, a campus or other relatively small geographic space), a telephone network, a data network associated with a telephone/voice provider (e.g., a mobile communications provider data and/or voice network), a direct connection between two computing devices, and any combinations thereof. A network may employ a wired and/or a wireless mode of communication. In general, any network topology may be used. Information (e.g., data, software etc.) may be communicated to and/or from a computer and/or a computing device. computing device 112 may include but is not limited to, for example, a computing device or cluster of computing devices in a first location and a second computing device or cluster of computing devices in a second location. computing device 112 may include one or more computing devices dedicated to data storage, security, distribution of traffic for load balancing, and the like. computing device 112 may distribute one or more computing tasks as described below across a plurality of computing devices of computing device, which may operate in parallel, in series, redundantly, or in any other manner used for distribution of tasks or memory between computing devices. computing device 112 may be implemented using a “shared nothing” architecture in which data is cached at the worker, in an embodiment, this may enable scalability of system 100 and/or computing device.

With continued reference to FIG. 1 , computing device 112 may be designed and/or configured to perform any method, method step, or sequence of method steps in any embodiment described in this disclosure, in any order and with any degree of repetition. For instance, computing device 112 may be configured to perform a single step or sequence repeatedly until a desired or commanded outcome is achieved; repetition of a step or a sequence of steps may be performed iteratively and/or recursively using outputs of previous repetitions as inputs to subsequent repetitions, aggregating inputs and/or outputs of repetitions to produce an aggregate result, reduction or decrement of one or more variables such as global variables, and/or division of a larger processing task into a set of iteratively addressed smaller processing tasks. computing device 112 may perform any step or sequence of steps as described in this disclosure in parallel, such as simultaneously and/or substantially simultaneously performing a step two or more times using two or more parallel threads, processor cores, or the like; division of tasks between parallel threads and/or processes may be performed according to any protocol suitable for division of tasks between iterations. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of various ways in which steps, sequences of steps, processing tasks, and/or data may be subdivided, shared, or otherwise dealt with using iteration, recursion, and/or parallel processing.

With continued reference to FIG. 1 computing device 112 and/or flight controller may be controlled by one or more Proportional-Integral-Derivative (PID) algorithms driven, for instance and without limitation by stick, rudder and/or thrust control lever with analog to digital conversion for fly by wire as described herein and related applications incorporated herein by reference. A “PID controller”, for the purposes of this disclosure, is a control loop mechanism employing feedback that calculates an error value as the difference between a desired setpoint and a measured process variable and applies a correction based on proportional, integral, and derivative terms; integral and derivative terms may be generated, respectively, using analog integrators and differentiators constructed with operational amplifiers and/or digital integrators and differentiators, as a non-limiting example. A similar philosophy to attachment of flight control systems to sticks or other manual controls via pushrods and wire may be employed except the conventional surface servos, steppers, or other electromechanical actuator components may be connected to the cockpit inceptors via electrical wires. Fly-by-wire systems may be beneficial when considering the physical size of the aircraft, utility of for fly by wire for quad lift control and may be used for remote and autonomous use, consistent with the entirety of this disclosure. Computing device 112 may harmonize vehicle flight dynamics with best handling qualities utilizing the minimum amount of complexity whether it be additional modes, augmentation, or external sensors as described herein.

With continued reference to FIG. 1 , computing device 112 may be configured to receive vehicle data 108 from sensor 104. A “sensor,” for the purposes of this disclosure, refer to a computing device configured to detect, capture, measure, or combination thereof, a plurality of external and electric vehicle component quantities. Sensor 104 may be integrated and/or connected to at least an actuator, a portion thereof, or any subcomponent thereof. Any datum or signal herein may include an electrical signal. Electrical signals may include analog signals, digital signals, periodic or aperiodic signal, step signals, unit impulse signal, unit ramp signal, unit parabolic signal, signum function, exponential signal, rectangular signal, triangular signal, sinusoidal signal, sinc function, or pulse width modulated signal. Sensor 104 may include circuitry or electronic components configured to digitize, transform, or otherwise manipulate electrical signals. Sensor 104 may be configured to be communicatively connected to the computing device. “Communicatively connected,” for the purposes of this disclosure, refers to two or more components electrically, or otherwise connected and configured to transmit and receive signals from one another. Signals may include electrical, electromagnetic, visual, audio, radio waves, or another undisclosed signal type alone or in combination.

With continued reference to FIG. 1 , sensor 104 may include a plurality of sensors in the form of individual sensors or a sensor suite working in tandem or individually. A sensor suite may include a plurality of independent sensors, as described herein, where any number of the described sensors may be used to detect any number of physical or electrical quantities associated with an aircraft power system or an electrical energy storage system. Independent sensors may include separate sensors measuring physical or electrical quantities that may be powered by and/or in communication with circuits independently, where each may signal sensor output to a control circuit such as a user graphical interface. In an embodiment, use of a plurality of independent sensors may result in redundancy configured to employ more than one sensor that measures the same phenomenon, those sensors being of the same type, a combination of, or another type of sensor not disclosed, so that in the event one sensor fails, the ability to detect phenomenon is maintained and in a non-limiting example, a user alter aircraft usage pursuant to sensor readings. Sensor may be configured to detect pilot input from at least pilot control. At least pilot control may include a throttle lever, inceptor stick, collective pitch control, steering wheel, brake pedals, pedal controls, toggles, joystick. One of ordinary skill in the art, upon reading the entirety of this disclosure would appreciate the variety of. Collective pitch control may be consistent with disclosure of collective pitch control in U.S. patent application Ser. No. 16/929,206 and titled “HOVER AND THRUST CONTROL ASSEMBLY FOR DUAL-MODE AIRCRAFT”, which is incorporated herein by reference in its entirety.

Sensor 104 may be mechanically and communicatively connected to one or more throttles. The throttle may be any throttle as described herein, and in non-limiting examples, may include pedals, sticks, levers, buttons, dials, touch screens, one or more computing devices, and the like. Additionally, a right-hand floor-mounted lift lever may be used to control the amount of thrust provided by the lift fans or other propulsors. The rotation of a thumb wheel pusher throttle may be mounted on the end of this lever and may control the amount of torque provided by the pusher motor, or one or more other propulsors, alone or in combination. Any throttle as described herein may be consistent with any throttle described in U.S. patent application Ser. No. 16/929,206 and titled, “Hover and Thrust Control Assembly for Dual-Mode Aircraft”, which is incorporated herein in its entirety by reference. Sensor 104 may be mechanically and communicatively connected to an inceptor stick. The pilot input may include a left-hand strain-gauge style STICK for the control of roll, pitch and yaw in both forward and assisted lift flight. A 4-way hat switch on top of the left-hand stick enables the pilot to set roll and pitch trim. Any inceptor stick described herein may be consistent with any inceptor or directional control as described in U.S. patent application Ser. No. 17/001,845 and titled, “A Hover and Thrust Control Assembly for a Dual-Mode Aircraft”, which is incorporated herein in its entirety by reference.

With continued reference to FIG. 1 , sensor 104 may include a motion sensor. A “motion sensor”, for the purposes of this disclosure is a device or component configured to detect physical movement of an object or grouping of objects. One of ordinary skill in the art would appreciate, after reviewing the entirety of this disclosure, that motion may include a plurality of types including but not limited to: spinning, rotating, oscillating, gyrating, jumping, sliding, reciprocating, or the like. Sensor 104 may include, but not limited to, torque sensor, gyroscope, accelerometer, magnetometer, inertial measurement unit (IMU), pressure sensor, force sensor, proximity sensor, displacement sensor, vibration sensor, LIDAR sensor, and the like. In a non-limiting embodiment sensor 104 ranges may include a technique for the measuring of distances or slant range from an observer including sensor 104 to a target which may include a plurality of outside parameters. “Outside parameter,” for the purposes of this disclosure, refer to environmental factors or physical electric vehicle factors including health status that may be further be captured by a sensor 104. Outside parameter may include, but not limited to air density, air speed, true airspeed, relative airspeed, temperature, humidity level, and weather conditions, among others. Outside parameter may include velocity and/or speed in a plurality of ranges and direction such as vertical speed, horizontal speed, changes in angle or rates of change in angles like pitch rate, roll rate, yaw rate, or a combination thereof, among others. Outside parameter may further include physical factors of the components of the electric aircraft itself including, but not limited to, remaining fuel or battery. Outside parameter may include at least an environmental parameter. Environmental parameter may be any environmentally based performance parameter as disclosed herein. Environment parameter may include, without limitation, time, pressure, temperature, air density, altitude, gravity, humidity level, airspeed, angle of attack, and debris, among others. Environmental parameters may be stored in any suitable datastore consistent with this disclosure. Environmental parameters may include latitude and longitude, as well as any other environmental condition that may affect the landing of an electric aircraft. Technique may include the use of active range finding methods which may include, but not limited to, light detection and ranging (LIDAR), radar, sonar, ultrasonic range finding, and the like. In a non-limiting embodiment, sensor 104 may include at least a LIDAR system to measure ranges including variable distances from the sensor 104 to a potential landing zone or flight path. LIDAR systems may include, but not limited to, a laser, at least a phased array, at least a microelectromechanical machine, at least a scanner and/or optic, a photodetector, a specialized GPS receiver, and the like. In a non-limiting embodiment, sensor 104 including a LIDAR system may target an object with a laser and measure the time for at least a reflected light to return to the LIDAR system. LIDAR may also be used to make digital 4-D representations of areas on the earth's surface and ocean bottom, due to differences in laser return times, and by varying laser wavelengths. In a non-limiting embodiment the LIDAR system may include a topographic LIDAR and a bathymetric LIDAR, wherein the topographic LIDAR that may use near-infrared laser to map a plot of a land or surface representing a potential landing zone or potential flight path while the bathymetric LIDAR may use water-penetrating green light to measure seafloor and various water level elevations within and/or surrounding the potential landing zone. In a non-limiting embodiment, electric aircraft may use at least a LIDAR system as a means of obstacle detection and avoidance to navigate safely through environments to reach a potential landing zone. Sensor 104 may include a sensor suite which may include a plurality of sensors that may detect similar or unique phenomena. For example, in a non-limiting embodiment, sensor suite may include a plurality of accelerometers, a mixture of accelerometers and gyroscopes, or a mixture of an accelerometer, gyroscope, and torque sensor.

With continued reference to FIG. 1 , sensor 104 may be configured to transmit vehicle data 108 to computing device 108. Sensor 104 may include a plurality of physical controller area network buses communicatively connected to the vehicle, such as an electronic vertical take-off and landing (eVTOL) aircraft as described in further detail below. A “physical controller area network bus,” as used in this disclosure, is vehicle bus unit including a central processing unit (CPU), a CAN controller, and a transceiver designed to allow devices to communicate with each other's applications without the need of a host computer which is located physically at the aircraft. For instance and without limitation, CAN bus unit may be consistent with disclosure of CAN bus unit in U.S. patent application Ser. No. 17/218,342 and titled “METHOD AND SYSTEM FOR VIRTUALIZING A PLURALITY OF CONTROLLER AREA NETWORK BUS UNITS COMMUNICATIVELY CONNECTED TO AN AIRCRAFT,” which is incorporated herein by reference in its entirety. Physical controller area network (CAN) bus unit may include physical circuit elements that may use, for instance and without limitation, twisted pair, digital circuit elements/FGPA, microcontroller, or the like to perform, without limitation, processing and/or signal transmission processes and/or tasks; circuit elements may be used to implement CAN bus components and/or constituent parts as described in further detail below. Physical CAN bus unit may include multiplex electrical wiring for transmission of multiplexed signaling. Physical CAN bus unit may include message-based protocol(s), wherein the invoking program sends a message to a process and relies on that process and its supporting infrastructure to then select and run appropriate programing. A plurality of physical CAN bus units located physically at the aircraft may include mechanical connection to the aircraft, wherein the hardware of the physical CAN bus unit is integrated within the infrastructure of the aircraft. Physical CAN bus units may be communicatively connected to the aircraft and/or with a plurality of devices outside of the aircraft, as described in further detail below.

With continued reference to FIG. 1 , sensor 104 may include a recording device. A “recording device, for the purpose of this disclosure, may be any device such as a camera, tape recorder, storage device, and the like, used to record any data describing a vehicle and its internal and external factors. In a non-limiting embodiment, recording device may include a flight recorder, audio tape recorder, storage recorder, black box, and the like thereof. In a non-limiting embodiment, recording device may include a metal foil and photographic film recorder, magnetic tape recorders, acquisition unit, solid state recorders, non-protected recorders, and the like thereof. In a non-limiting embodiment, recording device may include a cockpit voice recorder (CVR) disposed on the cockpit of a vehicle and configured to preserve the recent history of the sounds in the cockpit, including the conversation of one or more pilots. The two devices may be combined into a single unit. In a non-limiting embodiment, the FDR and CVR objectively document the aircraft's flight history, which may assist in any later investigation. For example and without limitation, the recording device may receive inputs via specific data frames from the Flight Data Acquisition Units (FDAU). Recorded data may include significant flight parameters, including the control and actuator positions, engine information and time of day. For example and without limitation, each parameter is recorded a few times per second, though some units store “bursts” of data at a much higher frequency if the data begin to change quickly. For example and without limitation, flight recorder may record approximately 17-25 hours of data in a continuous loop. In a non-limiting embodiment, recording device may be double wrapped in strong corrosion-resistant stainless steel or titanium, with high-temperature insulation inside. In a non-limiting embodiment, recording device may include an underwater locator beacon that emits an ultrasonic “ping” to aid in detection when submerged. For example and without limitation, the underwater locator beacon may operate for up to 30 days and are able to operate while immersed to a depth of up to 6,000 meters (20,000 ft). Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of the various embodiments of a recording device for purposes described herein.

Still referring to FIG. 1 , a plurality of physical CAN bus units communicatively connected to a vehicle such as an electric aircraft may include flight controller(s), battery terminals, gyroscope, accelerometer, proportional-integral-derivative controller, and the like, which may communicate directly with one another and to operating flight control devices, virtual machines, and other computing devices elsewhere. Physical CAN bus units may be mechanically connected to each other within the aircraft wherein the physical infrastructure of the device is integrated into the aircraft for control and operation of various devices within the aircraft. Physical CAN bus unit may be communicatively connected with each other and/or to one or more other devices, such as via a CAN gateway. Communicatively connecting may include direct electrical wiring, such as is done within automobiles and aircraft. Communicatively connecting may include infrastructure for receiving and/or transmitting transmission signals, such as with sending and propagating an analogue or digital signal using wired, optical, and/or wireless electromagnetic transmission medium.

With continued reference to FIG. 1 , computing device 112 may be configured to receive the vehicle data 108. A “vehicle data,” for the purpose of this disclosure, is an element of data describing the components that factor into the operation of a vehicle. In a non-limiting embodiment, vehicle data 108 may include a plurality of histories, records, projections, and the like thereof, regarding the operation of the vehicle. In a non-limiting embodiment, vehicle data 108 may include a plurality of records, reports, logs, and the like thereof, describing the performance history of the vehicle. In a non-limiting embodiment, vehicle data 108 may include information describing, but not limited to, vehicle personnel, vehicle capabilities, and the like thereof. In a non-limiting embodiment, vehicle data 108 may include information describing the maintenance, repair, and overhaul of a vehicle or a vehicle's components. In a non-limiting embodiment, vehicle data 108 may include a record of maintenance activities and their results including a plurality of tests, measurements, replacements, adjustments, repairs, and the like, that may be intended to retain and/or restore a functional unit of a vehicle. Vehicle data 108 may include a record of data of, but not limited to, functional checks, servicing, repairing or replacing of necessary devices, equipment, machinery, and the like, pertaining to the vehicle. In a non-limiting embodiment, vehicle data 108 may include a unique identification number denoting a part of a vehicle that was installed, repaired, or replaced as a function of a maintenance. In a non-limiting embodiment, vehicle data 108 may include a record of maintenance and/or repair schedules corresponding to a vehicle. The plurality of measured aircraft operation datum may include a record of potential maintenance and repair schedules corresponding to a vehicle. A “maintenance schedule,” for the purposes of this disclosure, refer to an appointment reserved for an aircraft for a maintenance or repair to be conducted upon. Vehicle data 108 may include any confidential information and/or data describing a vehicle and its operation. For example and without limitation, vehicle data 108 may include information classified by different level of confidentiality for specific users with different level of authority and/or access to confidential information. For example and without limitation, vehicle data 108 may include detailed information about the history and or background of a pilot of a vehicle which may be classified with a high classification label in which a user with a high classification label may access such information. For example and without limitation, information about flight destination, arrival, flight time, and the like thereof may be assigned a low classification label which may be available to any user with a low classification label and above. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of the various levels of information describing an electric aircraft as disclosed in the entirety of this disclosure.

With continued reference to FIG. 1 , the vehicle data 108 may include a flight component state data. A “flight component state data,” for the purposes of this disclosure, refer to any datum that represents the status or health status of a flight component or any component of an electric aircraft. The flight component state data of a plurality of flight components. “Flight components”, for the purposes of this disclosure, includes components related to, and mechanically connected to an aircraft that manipulates a fluid medium in order to propel and maneuver the aircraft through the fluid medium. The operation of the aircraft through the fluid medium will be discussed at greater length hereinbelow. In a non-limiting embodiment, the flight component state data may include a plurality of state information of a plurality of flight components of the electric aircraft. A state information of the plurality of state information of the plurality of aircraft components may include an aircraft flight duration, a distance of the aircraft flight, a plurality of distances of an aircraft from the surface, and the like. The flight component state data may denote a location of the aircraft, status of the aircraft such as health and/or functionality, aircraft flight time, aircraft on frame time, and the like thereof. The flight component state data may include aircraft logistics of an electric aircraft of a plurality of electrical aircraft.

With continued reference to FIG. 1 , vehicle data 108 may include at least an input datum. At least an “input datum,” for the purpose of this disclosure, is any datum or element of data identifying and/or a pilot input or command. At least pilot control may be communicatively connected to any other component presented in system, the communicative connection may include redundant connections configured to safeguard against single-point failure. Pilot input may indicate a pilot's desire to change the heading or trim of an electric aircraft. Pilot input may indicate a pilot's desire to change an aircraft's pitch, roll, yaw, or throttle. Aircraft trajectory is manipulated by one or more control surfaces and propulsors working alone or in tandem consistent with the entirety of this disclosure, hereinbelow. Pitch, roll, and yaw may be used to describe an aircraft's attitude and/or heading, as they correspond to three separate and distinct axes about which the aircraft may rotate with an applied moment, torque, and/or other force applied to at least a portion of an aircraft. “Pitch”, for the purposes of this disclosure refers to an aircraft's angle of attack, that is the difference between the aircraft's nose and the horizontal flight trajectory. For example, an aircraft pitches “up” when its nose is angled upward compared to horizontal flight, like in a climb maneuver. In another example, the aircraft pitches “down”, when its nose is angled downward compared to horizontal flight, like in a dive maneuver. When angle of attack is not an acceptable input to any system disclosed herein, proxies may be used such as pilot controls, remote controls, or sensor levels, such as true airspeed sensors, pitot tubes, pneumatic/hydraulic sensors, and the like. “Roll” for the purposes of this disclosure, refers to an aircraft's position about its longitudinal axis, that is to say that when an aircraft rotates about its axis from its tail to its nose, and one side rolls upward, like in a banking maneuver. “Yaw”, for the purposes of this disclosure, refers to an aircraft's turn angle, when an aircraft rotates about an imaginary vertical axis intersecting the center of the earth and the fuselage of the aircraft. “Throttle”, for the purposes of this disclosure, refers to an aircraft outputting an amount of thrust from a propulsor. Pilot input, when referring to throttle, may refer to a pilot's desire to increase or decrease thrust produced by at least a propulsor. In a non-limiting embodiment, input datum may include an electrical signal. In a non-limiting embodiment, input datum may include mechanical movement of any throttle consistent with the entirety of this disclosure. Electrical signals may include analog signals, digital signals, periodic or aperiodic signal, step signals, unit impulse signal, unit ramp signal, unit parabolic signal, signum function, exponential signal, rectangular signal, triangular signal, sinusoidal signal, sinc function, or pulse width modulated signal. At least a sensor may include circuitry, computing devices, electronic components or a combination thereof that translates pilot input into the at least an input datum configured to be transmitted to any other electronic component. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of the various inputs of a pilot or user as disclosed in the entirety of this disclosure.

With continued reference to FIG. 1 , the plurality of vehicle data may include at least a flight datum. At least a “flight datum,” for the purpose of this disclosure, is any datum or element of data describing physical parameters of individual actuators and/or flight components of an electric aircraft or logistical parameters of the electric aircraft. In a non-limiting embodiment, flight datum may include a plurality of data describing the health status of an actuator of a plurality of actuators. In a non-limiting embodiment, the plurality of data may include a plurality of failure data for a plurality of actuators. In a non-limiting embodiment, safety datum may include a measured torque parameter that may include the remaining vehicle torque of a flight component among a plurality of flight components. A “measured torque parameter,” for the purposes of this disclosure, refer to a collection of physical values representing a rotational equivalence of linear force. A person of ordinary skill in the art, after viewing the entirety of this disclosure, would appreciate the various physical factors in measuring torque of an object. For instance and without limitation, remaining vehicle torque may be consistent with disclosure of remaining vehicle torque in U.S. patent application Ser. No. 17/197,427 and titled “SYSTEM AND METHOD FOR FLIGHT CONTROL IN ELECTRIC AIRCRAFT”, which is incorporated herein by reference in its entirety. Remaining vehicle torque may include torque available at each of a plurality of flight components at any point during an aircraft's entire flight envelope, such as before, during, or after a maneuver. For example, and without limitation, torque output may indicate torque a flight component must output to accomplish a maneuver; remaining vehicle torque may then be calculated based on one or more of flight component limits, vehicle torque limits, environmental limits, or a combination thereof. Vehicle torque limit may include one or more elements of data representing maxima, minima, or other limits on vehicle torques, forces, attitudes, rates of change, or a combination thereof. Vehicle torque limit may include individual limits on one or more flight components, structural stress or strain, energy consumption limits, or a combination thereof. Remaining vehicle torque may be represented, as a non-limiting example, as a total torque available at an aircraft level, such as the remaining torque available in any plane of motion or attitude component such as pitch torque, roll torque, yaw torque, and/or lift torque. In a non-limiting embodiment, computing device 112 may mix, refine, adjust, redirect, combine, separate, or perform other types of signal operations to translate pilot desired trajectory into aircraft maneuvers. In a nonlimiting embodiment a pilot may send a pilot input at a press of a button to capture current states of the outside environment and subsystems of the electric aircraft to be displayed onto an output device in pilot view. The captured current state may further display a new focal point based on that captured current state. In a non-limiting embodiment, computing device 112 may condition signals such that they can be sent and received by various components throughout the electric vehicle. In a non-limiting embodiment, flight datum may include at least an aircraft angle. At least an aircraft angle may include any information about the orientation of the aircraft in three-dimensional space such as pitch angle, roll angle, yaw angle, or some combination thereof. In non-limiting examples, at least an aircraft angle may use one or more notations or angular measurement systems like polar coordinates, cartesian coordinates, cylindrical coordinates, spherical coordinates, homogenous coordinates, relativistic coordinates, or a combination thereof, among others. In a non-limiting embodiment, flight datum may include at least an aircraft angle rate. At least an aircraft angle rate may include any information about the rate of change of any angle associated with an electrical aircraft as described herein. Any measurement system may be used in the description of at least an aircraft angle rate.

With continued reference to FIG. 1 , in a non-limiting embodiment, computing device 112 may be responsible only for mapping the pilot inputs such as the at least an input datum, attitude such as at least an aircraft angle, and body angular rate measurement such as at least an aircraft angle rate to motor torque levels necessary to meet the at least an input datum. In a non-limiting exemplary embodiment, computing deice 112 may include the nominal attitude command (ACAH) configuration, the computing deice 112 may make the vehicle attitude track the pilot attitude while also applying the pilot-commanded amount of assisted lift and pusher torque which may be encapsulated within aircraft collection datum 124. The flight controller is responsible only for mapping the pilot inputs, attitude, and body angular rate measurements to motor torque levels necessary to meet the input datum 108. In the nominal attitude command (ACAH) configuration, computing deice 112 makes the vehicle attitude track the pilot attitude while also applying the pilot commanded amount of assisted lift and pusher torque. Computing deice 112 may include the calculation and control of avionics display of critical envelope information i.e., stall warning, vortex ring state, pitch limit indicator, angle of attack, transition envelopes, etc. Computing deice 112 may calculate, command, and control trim assist, turn coordination, pitch to certain gravitational forces, automation integration: attitude, position hold, LNAV, VNAV etc., minimum hover thrust protection, angle of attack limits, etc., precision Autoland, other aspects of autopilot operations, advanced perception of obstacles for ‘see and avoid’ missions, and remote operations, among others. Computing device 112 includes computing deice 112, wherein the computing deice 112 may further include a processor. The processor may include one or more processors as described herein, in a near limitless arrangement of components.

With continued reference to FIG. 1 , the vehicle data 108 may include at least a sensor datum. At least a “sensor datum,” for the purpose of this disclosure, is any datum or element of data describing parameters captured by a sensor describing the outside environment and physical values describing the performance or qualities of flight components of the electric aircraft. In a non-limiting embodiment, the at least a sensor datum may include any data captured by any sensor as described in the entirety of this disclosure. Additionally and alternatively, the at least a sensor datum may include any element or signal of data that represents an electric aircraft route and various environmental or outside parameters. In a non-limiting embodiment, the at least sensor datum may include an element of that representing the safest, most efficient, shortest, or a combination thereof, flight path. In a non-limiting embodiment, the at least a sensor datum may include a degree of torque that may be sensed, without limitation, using load sensors deployed at and/or around a propulsor and/or by measuring back electromotive force (back EMF) generated by a motor driving the propulsor. In an embodiment, use of a plurality of independent sensors may result in redundancy configured to employ more than one sensor that measures the same phenomenon, those sensors being of the same type, a combination of, or another type of sensor not disclosed, so that in the event one sensor fails, the ability to detect phenomenon is maintained and in a non-limiting example, a user alter aircraft usage pursuant to sensor readings. One of ordinary skill in the art will appreciate, after reviewing the entirety of this disclosure, that motion may include a plurality of types including but not limited to: spinning, rotating, oscillating, gyrating, jumping, sliding, reciprocating, or the like.

With continued reference to FIG. 1 , the at least a sensor datum may include a detection of a network 116. A “network, for the purpose of this disclosure, is any medium configured to facilitate communication between two or more devices. Network 116 may include any network described in this disclosure, for example without limitation an avionic mesh network as described below. In a non-limiting embodiment, sensor 104 may transmit a signal using network 116 to computing device 112. Signal may be received by computing device 112. In a non-limiting embodiment, network 116 may be communicatively connected to sensor 104. In a non-limiting embodiment, network 116 may be communicatively connected to computing device 112 and at least the electric aircraft. In a non-limiting embodiment, network 116 may be communicatively connected to a second device 144. In some cases, network 112 may include a mesh network. In a non-limiting embodiment, network 116 may be communicatively connected to a second computing device such as a second vehicle. For example and without limitation, computing devices of the electric aircraft and second vehicle may transfer and/or store a plurality of data through radio frequency signals. In some cases, network 116 may communicated encrypted data. As used in this disclosure, “encrypted data” is any communicable information that is protected or secured by any method, including obfuscation, encryption, and the like. Encrypted data may include information protected by any cryptographic method described in this disclosure. In some embodiments, network 116 may include an intra-aircraft network and/or an inter-aircraft network. Intra-aircraft network may include any intra-aircraft network described in this disclosure. Inter-aircraft network may include any inter-aircraft network described in this disclosure.

With continued reference to FIG. 1 , computing device 112 may be configured to determine a connection. A “connection,” for the purpose of this disclosure, is any connection that links two or more computing devices through a network or any electrical signal. In a non-limiting embodiment, the connection may include an internet connection. In a non-limiting embodiment, the connection may include a connection with second device 144. A “second device,” for the purpose of this disclosure, is any device, vehicle, computing device, and the like thereof that may be connected to computing device 112 of the vehicle of system 100. For example and without limitation, second device 144 may include a remote device in which the remote device may detect and form a connection with another aircraft 140 in the air. In another non-limiting example, second device 144 may include a user device. A “user device,” for the purpose of this disclosure, may include a separate computing device that may be used to connect with computing device 112 for transmitting and receiving vehicle data 108. In a non-limiting embodiment, the user device may include an additional computing device, such as a mobile device, laptop, desktop computer, or the like; as a non-limiting example, the user device may be a computer and/or smart phone operated by a pilot-in-training at an airport hangar. The user device may include, without limitation, a display in communication with computing device 112; the display may include any display as described in the entirety of this disclosure such as a light emitting diode (LED) screen, liquid crystal display (LCD), organic LED, cathode ray tube (CRT), touch screen, or any combination thereof. Vehicle collection datum 124 may be configured to be displayed on user device using an output graphical user interface. An output graphical user interface may display any output as described in the entirety of this disclosure. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of the various embodiments and functions of a second device such as a user device in connecting and communicating with computing device 112 as described in the entirety of this disclosure.

With continued reference to FIG. 1 , in another non-limiting embodiment, the vehicle of system 100 may include computing device 112 in which it detects a remote device via network 116 and form a connection with the remote device. In a non-limiting embodiment, connection may include a connection with a second vehicle. For example and without limitation, the electric aircraft may detect network 116 during flight and detect another aircraft 140 and form a connection with second vehicle 140. A “second vehicle,” for the purpose of this disclosure, may be any other vehicle including an electric aircraft that may be connected with computing device 112 and the vehicle of system 100. Computing device 112 may communicatively connect the electric aircraft and the computing device as a function of a mesh network. Connecting may include forming the connection wherein the connection may include any connection as described in the entirety of this disclosure. Computing device 112 may communicatively connect the vehicle of system 100 and computing device 112 as a function of a mesh network. Connecting may include forming the connection wherein the connection may include any connection as described in the entirety of this disclosure. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of the various embodiments of detecting, determining, and forming a connection between two or more computing devices and the various networks and connections used as disclosed in the entirety of this disclosure.

With continued reference to FIG. 1 , computing device 112 may be configured to authenticate second device 144 as a function of authentication module 132. Computing device 112 may be configured to authenticate second vehicle 140. In a non-limiting embodiment, once computing device 112 has established a connection with another device, via network 116 or any radio frequency or Bluetooth connection, computing device 112 may then verify if the device at the other end of the connection is a valid device with authorized access to receive vehicle data 108 and/or vehicle collection datum 124. In a non-limiting embodiment, authentication may be performed automatically via authentication module 132. In a non-limiting embodiment, authentication may be performed manually between operators of both devices through radio transmissions. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of the various purposes and methods of authenticating a second party as disclosed in the entirety of this disclosure.

With continued reference to FIG. 1 , computing device 112 may be configured to receive a credential associated with another device which may include second device 144 and/or second vehicle 140. In a non-limiting embodiment, another device may include a user device. In a non-limiting embodiment, computing device 112 may be configured to compare the credential from user device to an authorized credential stored within an authentication database, and bypass authentication for user device based on the comparison of the credential from user device to the authorized credential stored within the authentication database. A “credential” as described in the entirety of this disclosure, is any datum representing an identity, attribute, code, and/or characteristic specific to a user and/or user device. For example and without limitation, the credential may include a username and password unique to the user and/or user device. The username and password may include any alpha-numeric character, letter case, and/or special character. As a further example and without limitation, the credential may include a digital certificate, such as a PKI certificate. User device may include an additional computing device, such as a mobile device, laptop, desktop computer, or the like; as a non-limiting example, the user device may be a computer and/or smart phone operated by a pilot-in-training at an airport hangar. User device may include, without limitation, a display in communication with computing device 112; the display may include any display as described in the entirety of this disclosure such as a light emitting diode (LED) screen, liquid crystal display (LCD), organic LED, cathode ray tube (CRT), touch screen, or any combination thereof. Output data from computing device 112 may be configured to be displayed on user device using an output graphical user interface. An output graphical user interface may display any output as described in the entirety of this disclosure. Further, authentication module 132 and/or computing device 112 may be configured to receive a credential from an instructor device. The instructor device may include any additional computing device as described above, wherein the additional computing device is utilized by and/or associated with a certified flight instructor. As a further embodiment, authentication module 132 and/or computing device 112 may be configured to receive a credential from an admin device. The admin device may include any additional computing device as described above in further detail, wherein the additional computing device is utilized by/associated with an employee of an administrative body, such as an employee of the federal aviation administration.

With continued reference to FIG. 1 , computing device 112 may be configured to generate vehicle collection datum 124. A “vehicle collection datum,” for the purpose of this disclosure, is a datum or element of data such as vehicle data 108 that is organized, analyzed, and/or normalized into a collection of data. In a non-limiting embodiment, vehicle collection datum may include a plurality of subsets of normalized vehicle data 108. For example and without limitation, computing device 112 may map a plurality of data from vehicle data 108 and map each data to a specific vehicle performance parameter. In a non-limiting embodiment, vehicle collection datum 124 is an organized set of data categorizing vehicle data 108 such as sparse sets of vehicle data 108. A “vehicle performance parameter,” for the purpose of this disclosure, is any parameter regarding the performance of the flight components of an electric aircraft of the vehicle of system 100. In a non-limiting embodiment, the vehicle performance parameter may include torque output, aircraft angle, aircraft attitude, aircraft power consumption rate, and the like thereof. Vehicle collection datum 108 may include groupings of vehicle data assigned to the performance of specific flight components of the electric aircraft. Vehicle collection datum 108 may include, but not limited to, a summary, conclusion, recommendation, suggestion, or any combination thereof. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of the various embodiments and methods of analyzing a plurality of inputs and data for purposes described herein.

With continued reference to FIG. 1 , vehicle collection datum 120 may include vehicle model output 120. A “vehicle model output,” for the purpose of this disclosure, is an analytical and/or interactive visualization regarding vehicle operation and/or performance capabilities. In a non-limiting embodiment, vehicle model output 120 may include a model depicting the performance of the aircraft in which one or more of the actuators are malfunctioning or failing. In a non-limiting embodiment, vehicle model output 120 may be generated during a flight or after a flight has occurred. For example and without limitation, vehicle model output 120 may depict the performance of the aircraft and the aircraft actuators in real time as it is flying in the air. In a non-limiting embodiment, vehicle model output 120 may include a depiction of the flight of the vehicle and/or aircraft. In a non-limiting embodiment, vehicle model output 120 may include a plurality of performance parameters include, but not limited to, aircraft velocity, attitude, actuator torque output, and the like thereof. In a non-limiting embodiment, vehicle model output 120 may highlight an abnormality of an actuator and a plurality of performance parameters associated with that abnormal actuator. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of the various embodiments of a simulation and/or model in the context of visualization and analysis consistent with this disclosure.

With continued reference to FIG. 1 , vehicle model output 120 may be generated as a function of a vehicle simulator. A “vehicle simulator” is a program or set of operations that simulate flight of a vehicle including an aircraft. In some cases, vehicle simulator may include a flight simulator which may simulate flight within an environment, for example an environmental atmosphere in which aircraft fly, airports at which aircraft take-off and land, and/or mountains and other hazards aircraft attempt to avoid crashing into. For instance and without limitation, flight simulator may be consistent with flight simulator in U.S. patent application Ser. No. 17/348,916 and titled “METHODS AND SYSTEMS FOR SIMULATED OPERATION OF AN ELECTRIC VERTICAL TAKE-OFF AND LANDING (EVTOL) AIRCRAFT,” which is incorporated herein by reference in its entirety. In some cases, an environment may include geographical, atmospheric, and/or biological features. In some cases, the vehicle simulator may model an artificial and/or virtual aircraft in flight as well as an environment in which the artificial and/or virtual aircraft flies. In some cases, the flight simulator may include one or more physics models, which represent analytically or through data-based, such as without limitation machine-learning processes, physical phenomenon. Physical phenomenon may be associated with an aircraft and/or an environment. For example, some versions of the vehicle simulator may include thermal models representing aircraft components by way of thermal modeling. Thermal modeling techniques may, in some cases, include analytical representation of one or more of convective hear transfer (for example by way of Newton's Law of Cooling), conductive heat transfer (for example by way of Fourier conduction), radiative heat transfer, and/or advective heat transfer. In some cases, the vehicle simulator may include models representing fluid dynamics. For example, in some embodiments, flight simulator may include a representation of turbulence, wind shear, air density, cloud, precipitation, and the like. In some embodiments, the vehicle simulator may include at least a model representing optical phenomenon. For example, the vehicle simulator may include optical models representative of transmission, reflectance, occlusion, absorption, attenuation, and scatter. The vehicle simulator may include non-analytical modeling methods; for example, the flight simulator may include, without limitation, a Monte Carlo model for simulating optical scatter within a turbid medium, for example clouds. In some embodiments, the vehicle simulator may represent Newtonian physics, for example motion, pressures, forces, moments, and the like. An exemplary flight simulator may include Microsoft Flight Simulator from Microsoft of Redmond, Wash., U.S.A.

With continued reference to FIG. 1 , the vehicle simulator may be configured to generate an expected vehicle model output. An “expected vehicle model output,” for the purpose of this disclosure, is any vehicle model output of the aircraft that embodies an ideal or expected analytical and/or interactive visualization regarding aircraft operation and/or performance capabilities. In a non-limiting embodiment, the expected vehicle model output may include a vehicle model output that depicts a performance model in which none of the actuators are malfunctioning. For example and without limitation, the expected vehicle model output may be a model depicting a performance of what the aircraft should be based on the ideal, expected, or initial performance the aircraft actuators are intended to perform. For example and without limitation, the expected vehicle model output includes peak performance output including, but not limited to, power consumption, maximum torque output, cruising torque output, maximum attitude, cruising attitude, maximum velocity, cruising velocity, and the like thereof. For example and without limitation, the expected vehicle model output may highlight individual performance parameters of each actuator based on a sensor disposed on each actuator. In a non-limiting embodiment, the expected vehicle model output can be used to assess the performance of the aircraft actuators by comparing the expected vehicle model output to vehicle model output 120 and analyzing the difference between the data from the two models. In a non-limiting embodiment, computing device 112 may feed the vehicle simulator the ideal and/or peak performance parameters of an aircraft and its actuators to simulate the expected vehicle model output based on those ideal and/or peak performance parameters. In a non-limiting embodiment, the expected vehicle model output may include a plurality of the expected vehicle model output depicting a different failure modes of an aircraft and/or an aircraft's actuators. For example and without limitation, a rotor may fail by outputting max thrust, outputting zero thrust, or be stuck at an intermediate setting. In some embodiments, models are determined based on and/or for various actuator settings. In various embodiments, only highly likely or relatively dangerous actuator failure modes are considered and modeled. For example, a rotor may be modeled for a zero-output case but not for a pinned high case. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of the various models and comparisons consistent with this disclosure.

With continued reference to FIG. 1 , the vehicle simulator may be configured to simulate a virtual representation. The virtual representation may represent a virtualization of vehicle model output 120 and/or the expected vehicle model output. As described in this disclosure, a “virtual representation” includes any model or simulation accessible by computing device 112 which is representative of a physical phenomenon experienced by an aircraft, vehicle, and the like thereof. In some cases, virtual representation may be interactive with the vehicle simulator. For example, in some cases, data may originate from virtual representation and be input into the vehicle simulator. Alternatively or additionally, in some cases, the virtual representation may modify or transform data already available to the vehicle simulator. In some cases, at least the virtual representation may include a virtual controller area network. Virtual controller area network may include any virtual controller area network as described in this disclosure, for example below. In some cases, aircraft digital twin may include a flight controller model. Flight controller model may include any flight controller model described in this disclosure. Alternatively or additionally, in some cases, the virtual representation may modify or transform data already available to the vehicle simulator. The virtual representation may include an electric aircraft and/or one or more actuator of the electric aircraft. In some cases, at least electric aircraft may include an electric vertical take-off and landing (eVTOL) aircraft, for example a functional flight-worthy eVTOL aircraft. In some cases, at least a virtual representation may include a virtual controller area network. Virtual controller area network may include any virtual controller area network. A controller area network may include a plurality of physical controller area network buses communicatively connected to the aircraft, such as an electronic vertical take-off and landing (eVTOL) aircraft as described in further detail below. A physical controller area network bus may be vehicle bus unit including a central processing unit (CPU), a CAN controller, and a transceiver designed to allow devices to communicate with each other's applications without the need of a host computer which is located physically at the aircraft. Physical controller area network (CAN) bus unit may include physical circuit elements that may use, for instance and without limitation, twisted pair, digital circuit elements/FGPA, microcontroller, or the like to perform, without limitation, processing and/or signal transmission processes and/or tasks; circuit elements may be used to implement CAN bus components and/or constituent parts as described in further detail below. Physical CAN bus unit may include multiplex electrical wiring for transmission of multiplexed signaling. Physical CAN bus unit may include message-based protocol(s), wherein the invoking program sends a message to a process and relies on that process and its supporting infrastructure to then select and run appropriate programing. A plurality of physical CAN bus units located physically at the aircraft may include mechanical connection to the aircraft, wherein the hardware of the physical CAN bus unit is integrated within the infrastructure of the aircraft. Physical CAN bus units may be communicatively connected to the aircraft and/or with a plurality of devices outside of the aircraft.

With continued reference to FIG. 1 , computing device 112 may be configured to determine a subset of received vehicle data from vehicle collection datum 124 to store, wherein the subset further comprises a plurality of vehicle model outputs 120. The subset may include a vehicle model output generated using vehicle data 108 received at different time intervals maintained by timer module 136. A “timer module,” for the purpose of this disclosure, is a timer configured to detect, as a function of time, loss of communication with another computing device or network. In a non-limiting embodiment, computing device 112 may include timer module 136 to time all communication to and from computing device 112 to network 116, second vehicle 140, and/or second device 144, to detect that computing device 112 has not transmitted vehicle collection datum 124 within a particular time limit, and thus, communication is likely lost. In a non-limiting embodiment, timer module 136 to time all communication to and from computing device 112 to network 116, second vehicle 140, and/or second device 144, to detect that computing device 112 has not formed a connection within a particular time limit, and thus, communication is likely lost. In a non-limiting embodiment, timer module 136 may be configured to instruct computing device 112 to close any communication ports and begin storing vehicle collection datum 124 and/or any remaining vehicle collection datum 124 leftover after a connection has been lost after a particular time limit. For example and without limitation, computing device 112 may lose connection with network 116 or any other device or vehicle and instruct timer module 136 to initiate a timer indicating the amount of time computing device 112 has remained isolated and/or unconnected. For example and without limitation, the timer may reach 3 minutes without locating any other connection in which computing device 112 may close any connection ports and begin storing any datum into recorder database 128. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of the various methods and embodiments for switching modes between transmitting and storing for purposes described herein.

With continued reference to FIG. 1 , computing device 112 may be configured to determine a subset of received vehicle data from vehicle collection datum 124 to store, wherein the subset further comprises a plurality of vehicle model outputs 120. The subset may include a vehicle model output generated using vehicle data 108 received at different time intervals maintained by timer module 136 as described herein. In a non-limiting embodiment, computing device 112 and at least a vehicle simulator may be configured to generate a vehicle model output with vehicle data 108 received until a specific time limit. For example and without limitation, timer module 136 may take intervals of every 3 minutes in which a vehicle model output 120 may be generated based on vehicle data 108 received at the interval while computing device 112 concurrently receives new vehicle data 108 in which a new vehicle model output is generated for the new vehicle data received for the next interval, creating a plurality of subset of vehicle data including a plurality of individual vehicle model outputs. While computing device 112 is performing the above actions, it may also be configured to transmit the subsets to another device via network 116 or any connection established. In a non-limiting embodiment, the subsets may represent a frame-by-frame simulation of the vehicle and/or aircraft and vehicle collection datum 124 for each respective frame to inform users the conditions surrounding the vehicle and/or aircraft at each frame during operation or flight. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of the various embodiments of multiple frames or subsets of organized data for the purposes of analysis, transmission, and storage as described in the entirety of this disclosure.

With continued reference to FIG. 1 , computing device 112 may lose connection with any source during flight of the aircraft. In a non-limiting embodiment, timer module 136 may begin a timer to denote how long a connection cannot be found in which once that timer limit has been reached, computing device 112 may store vehicle collection datum 124 and its subsets of vehicle data into recorder database 128. A “recorder database,” for the purpose of this disclosure, is any data storage system that stores any datum regarding the operation, communication, and environment of a vehicle and/or aircraft. Storing may include any storing as described in the entirety of this disclosure. In a non-limiting embodiment, recorder database 128 may include a black box or flight data recording (FDR) device. Recorder database 128 may store high resolution data. The flight data is stored on a computer memory. In a non-limiting embodiment, a subset of the vehicle data recording device data is saved to recorder database 128 either installed in the aircraft or a portable device. In the event a separate device is not used, a subset of vehicle data determined not to be saved is deleted from recorder database 128. At, a subset of the flight data is saved to a device (e.g. the separate device or the flight data recording device). The subset of the vehicle data may comprise data that is of interest to a pilot or aircraft company. In a non-limiting embodiment, vehicle data may be uploaded from recorder database 128 to an online network such as network 116 or another device via Bluetooth connection. The flight data may be downloaded from the online network and processed, with processed vehicle data uploaded back to the online network. In some embodiments, the vehicle data is processed on the network. For example and without limitation, processed flight data from the online network is received. The device may display processed vehicle data via an application installed on second device 144 such as a user device. In a non-limiting embodiment, computing device 112 may be configured to store any datum as described herein into recorder database 128 once a lack of connection has been established or confirmed as a function of timer module 136. In a non-limiting embodiment, recorder database 128 may be configured to use and/or support database encryption. A “database encryption,” for the purpose of this disclosure, is a process that uses algorithms to transform data stored in a database into cipher text. In a non-limiting embodiment, recorder database may incorporate encryption methods including, but not limited to, API method, plug-In Method, Transparent data encryption (TDE) method, and the like thereof. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of the various embodiments and functions of recorder database 128 and security measures as described in the entirety of this disclosure.

With continued reference to FIG. 1 , wherein the computing device is further configured to generate a machine-learning model. The machine-learning model may be configured to receive vehicle data 108 as an input and output vehicle model output 120 as a function of a training data. The machine-learning model may include a trained machine-learning model (e.g. a classifier) trained by the training set, wherein the training set contains a plurality of data entries including an element of a maneuver data correlated to an element of model data. An “element of maneuver data” as described in the entirety of this disclosure is data describing completion by the pilot of a vehicle of procedures and concepts that control the electric aircraft. The maneuver data may include a plurality of maneuver data. For example and without limitation, the plurality of maneuver data may include foundational vehicle maneuvers, such as straight-and-level turns, climbs and descents, and/or performance maneuvers, such that the application of vehicle control pressures, attitudes, airspeeds, and orientations are constantly changing throughout the maneuver. For example and without limitation, the plurality of maneuver data may include, ground reference maneuvers, such as turns around a point, s-turns, rectangular ground maneuvering course, eights along A road, eights around pylons, hover taxi, air taxi, surface taxi, and the like. As a further example and without limitation, the plurality of maneuver data may include takeoffs and landings, such as normal takeoff and climb, crosswind takeoff and climb, short field takeoff and climb, normal takeoff from a hover, vertical takeoff to a hover, short field approach and landing, soft field approach and landing, touch and go, power-off 180 approach and landing, normal approach to a hover, crosswind approach to the surface, and the like. The plurality of maneuver data may further include, for example and without limitation, airborne maneuvers, such as trimming the aircraft, slow flight, lazy eights, chandelle, straight and level flight, turns, steep turns, unusual attitudes, spatial disorientation demonstration, hovering, hovering turn, rapid deceleration, reconnaissance procedures, and the like. The plurality of maneuver data, as a further non-limiting example, may include emergency preparedness, such as steep spirals, emergency approach and landing, spins, ditching, autorotation, vortex ring state, retreating blade stall, ground resonance, dynamic rollover, low rotor RPM, systems malfunction, flight diversions, and the like. Further, the plurality of maneuver data may include, as a non-limiting example, instrument procedures, such as aircraft holding procedures, arcing approach, instrument landing system approach, instrument reference climbs and descents, basic attitude instrument flight, and the like. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of various procedures and concepts that may represent the plurality of maneuver data consistently with this disclosure. An “element of model data,” for the purpose of this disclosure, is data and/or classification describing any simulated vehicle model and/or virtual representation of a vehicle. In a non-limiting embodiment, the element of model data may include a single frame of a simulation. For example and without limitation, the machine-learning model may use the correlation to generate, which may include a combination of multiple frames of simulation and/or multiple frames of the element of model data, vehicle model output 120 as a function of the training set. In a non-limiting embodiment, the training data may include any entries or data retrieved from recorder database 128.

Referring now to FIG. 2 , an exemplary embodiment of a system 200 for mesh network for a vehicle is illustrated. System 200 may include a mesh network for an electric aircraft. System 200 may include a node 204. Node 204 may include any computing device as described in this disclosure, including without limitation a microcontroller, microprocessor, digital signal processor (DSP) and/or system on a chip (SoC) as described in this disclosure. Node 204 may include, be included in, and/or communicate with a mobile device such as a mobile telephone or smartphone. Node 204 may include a single computing device operating independently, or may include two or more computing device operating in concert, in parallel, sequentially or the like; two or more computing devices may be included together in a single computing device or in two or more computing devices. Node 204 may interface or communicate with one or more additional devices as described below in further detail via a network interface device. Network interface device may be utilized for connecting node 204 to one or more of a variety of networks, and one or more devices. Examples of a network interface device include, but are not limited to, a network interface card (e.g., a mobile network interface card, a LAN card), a modem, and any combination thereof. Examples of a network include, but are not limited to, a wide area network (e.g., the Internet, an enterprise network), a local area network (e.g., a network associated with an office, a building, a campus or other relatively small geographic space), a telephone network, a data network associated with a telephone/voice provider (e.g., a mobile communications provider data and/or voice network), a direct connection between two computing devices, and any combinations thereof. A network may employ a wired and/or a wireless mode of communication. In general, any network topology may be used. Information (e.g., data, software etc.) may be communicated to and/or from a computer and/or a computing device. Node 204 may include but is not limited to, for example, a computing device or cluster of computing devices in a first location and a second computing device or cluster of computing devices in a second location. Node 204 may include one or more computing devices dedicated to data storage, security, distribution of traffic for load balancing, and the like. Node 204 may distribute one or more computing tasks as described below across a plurality of computing devices of computing device, which may operate in parallel, in series, redundantly, or in any other manner used for distribution of tasks or memory between computing devices. Node 204 may be implemented using a “shared nothing” architecture in which data is cached at the worker, in an embodiment, this may enable scalability of system 200 and/or computing device.

With continued reference to FIG. 2 , node 204 may be designed and/or configured to perform any method, method step, or sequence of method steps in any embodiment described in this disclosure, in any order and with any degree of repetition. For instance, node 204 may be configured to perform a single step or sequence repeatedly until a desired or commanded outcome is achieved; repetition of a step or a sequence of steps may be performed iteratively and/or recursively using outputs of previous repetitions as inputs to subsequent repetitions, aggregating inputs and/or outputs of repetitions to produce an aggregate result, reduction or decrement of one or more variables such as global variables, and/or division of a larger processing task into a set of iteratively addressed smaller processing tasks. Node 204 may perform any step or sequence of steps as described in this disclosure in parallel, such as simultaneously and/or substantially simultaneously performing a step two or more times using two or more parallel threads, processor cores, or the like; division of tasks between parallel threads and/or processes may be performed according to any protocol suitable for division of tasks between iterations. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of various ways in which steps, sequences of steps, processing tasks, and/or data may be subdivided, shared, or otherwise dealt with using iteration, recursion, and/or parallel processing.

Still referring to FIG. 2 , in some embodiments, system 200 may include a network topology. A “network topology” as used in this disclosure is an arrangement of elements of a communication network. In some embodiments, system 200 may include, but is not limited to, a star network, tree network, and/or a mesh network. A “mesh network” as used in this disclosure is a local network topology in which the infrastructure nodes connect directly, dynamically, and non-hierarchically to one or more other nodes. Nodes of system 200 may be configured to communicate in a partial mesh network. A partial mesh network may include a communication system in which some nodes may be connected directly to one another while other nodes may need to connect to at least another node to reach a third node. In some embodiments, system 200 may be configured to communicate in a full mesh network. A full mesh network may include a communication system in which every node in the network may communicate directly to one another. In some embodiments, system 200 may include a layered data network. As used in this disclosure a “layered data network” is a data network with a plurality of substantially independent communication layers with each configured to allow for data transfer over predetermined bandwidths and frequencies. As used in this disclosure a “layer” is a distinct and independent functional and procedural tool of transferring data from one location to another. For example, and without limitation, one layer may transmit communication data at a particular frequency range while another layer may transmit communication data at another frequency range such that there is substantially no crosstalk between the two layers which advantageously provides a redundancy and safeguard in the event of a disruption in the operation of one of the layers. A layer may be an abstraction which is not tangible.

Still referring to FIG. 2 , in some embodiments, system 200 may include node 204, second node 208, third node 212, and/or fourth node 216. Node 204 may be configured to communicate with a first layer providing radio communication between nodes at a first bandwidth. In some embodiments, node 204 may be configured to communicate with a second layer providing mobile network communication between the nodes at a second bandwidth. In some embodiments, node 204 may be configured to communicate with a third layer providing satellite communication between the nodes at a third bandwidth. In some embodiments, any node of system 200 may be configured to communicate with any layer of communication. In some embodiments, a node of system 200 may include an antenna configured to provide radio communication between one or more nodes. For example, and without limitation, an antenna may include a directional antenna. In an embodiment, system 200 may include a first bandwidth, a second bandwidth, and a third bandwidth. In some embodiments, system 200 may include more or less than three bandwidths. In some embodiments, a first bandwidth may be greater than a second bandwidth and a third bandwidth. In some embodiments, system 200 may be configured to provide mobile network communication in the form a cellular network, such as, but not limited to, 2G, 3G, 4G, 5G, LTE, and/or other cellular network standards.

Still referring to FIG. 2 , radio communication, in accordance with embodiments, may utilize at least a communication band and communication protocols suitable for aircraft radio communication. For example, and without limitation, a very-high-frequency (VHF) air band with frequencies between about 208 MHz and about 237 MHz may be utilized for radio communication. In another example, and without limitation, frequencies in the Gigahertz range may be utilized. Airband or aircraft band is the name for a group of frequencies in the VHF radio spectrum allocated to radio communication in civil aviation, sometimes also referred to as VHF, or phonetically as “Victor”. Different sections of the band are used for radio-navigational aids and air traffic control. Radio communication protocols for aircraft are typically governed by the regulations of the Federal Aviation Authority (FAA) in the United States and by other regulatory authorities internationally. Radio communication protocols may employ, for example and without limitation an S band with frequencies in the range from about 2 GHz to about 4 GHz. For example, and without limitation, for 4G mobile network communication frequency bands in the range of about 2 GHz to about 8 GHz may be utilized, and for 5G mobile network communication frequency bands in the ranges of about 450 MHz to about 6 GHz and of about 24 GHz to about 53 GHz may be utilized. Mobile network communication may utilize, for example and without limitation, a mobile network protocol that allows users to move from one network to another with the same IP address. In some embodiments, a node of system 200 may be configured to transmit and/or receive a radio frequency transmission signal. A “radio frequency transmission signal,” as used in this disclosure, is an alternating electric current or voltage or of a magnetic, electric, or electromagnetic field or mechanical system in the frequency range from approximately 20 kHz to approximately 300 GHz. A radio frequency (RF) transmission signal may compose an analogue and/or digital signal received and be transmitted using functionality of output power of radio frequency from a transmitter to an antenna, and/or any RF receiver. A RF transmission signal may use longwave transmitter device for transmission of signals. An RF transmission signal may include a variety of frequency ranges, wavelength ranges, ITU designations, and IEEE bands including HF, VHF, UHF, L, S, C, X, Ku, K, Ka, V, W, mm, among others.

Still referring to FIG. 2 , satellite communication, in accordance with embodiments, may utilize at least a communication band and communication protocols suitable for aircraft satellite communication. For example, and without limitation, satellite communication bands may include L-band (1-2 GHz), C-band (4-8 GHz), X-band (8-12 GHz), Ku-band (12-18 GHz), Ku-band (12-18 GHz), and the like, among others. Satellite communication protocols may employ, for example and without limitation, a Secondary Surveillance Radar (SSR) system, automated dependent surveillance-broadcast (ADS-B) system, or the like. In SSR, radar stations may use radar to interrogate transponders attached to or contained in aircraft and receive information in response describing such information as aircraft identity, codes describing flight plans, codes describing destination, and the like SSR may utilize any suitable interrogation mode, including Mode S interrogation for generalized information. ADS-B may implement two communication protocols, ADS-B-Out and ADS-B-In. ADS-B-Out may transmit aircraft position and ADS-B-In may receive aircraft position. Radio communication equipment may include any equipment suitable to carry on communication via electromagnetic waves at a particular bandwidth or bandwidth range, for example and without limitation, a receiver, a transmitter, a transceiver, an antenna, an aerial, and the like, among others. A mobile or cellular network communication equipment may include any equipment suitable to carry on communication via electromagnetic waves at a particular bandwidth or bandwidth range, for example and without limitation, a cellular phone, a smart phone, a personal digital assistant (PDA), a tablet, an antenna, an aerial, and the like, among others. A satellite communication equipment may include any equipment suitable to carry on communication via electromagnetic waves at a particular bandwidth or bandwidth range, for example and without limitation, a satellite data unit, an amplifier, an antenna, an aerial, and the like, among others.

Still referring to FIG. 2 , as used in this disclosure “bandwidth” is measured as the amount of data that can be transferred from one point or location to another in a specific amount of time. The points or locations may be within a given network. Typically, bandwidth is expressed as a bitrate and measured in bits per second (bps). In some instances, bandwidth may also indicate a range within a band of wavelengths, frequencies, or energies, for example and without limitation, a range of radio frequencies which is utilized for a particular communication.

Still referring to FIG. 2 , as used in this disclosure “antenna” is a rod, wire, aerial or other device used to transmit or receive signals such as, without limitation, radio signals and the like. A “directional antenna” or beam antenna is an antenna which radiates or receives greater power in specific directions allowing increased performance and reduced interference from unwanted sources. Typical examples of directional antennas include the Yagi antenna, the log-periodic antenna, and the corner reflector antenna. The directional antenna may include a high-gain antenna (HGA) which is a directional antenna with a focused, narrow radio wave beamwidth and a low-gain antenna (LGA) which is an omnidirectional antenna with a broad radio wave beamwidth, as needed or desired.

With continued reference to FIG. 2 , as used in this disclosure, a “signal” is any intelligible representation of data, for example from one device to another. A signal may include an optical signal, a hydraulic signal, a pneumatic signal, a mechanical, signal, an electric signal, a digital signal, an analog signal and the like. In some cases, a signal may be used to communicate with a computing device, for example by way of one or more ports. In some cases, a signal may be transmitted and/or received by a computing device for example by way of an input/output port. An analog signal may be digitized, for example by way of an analog to digital converter. In some cases, an analog signal may be processed, for example by way of any analog signal processing steps described in this disclosure, prior to digitization. In some cases, a digital signal may be used to communicate between two or more devices, including without limitation computing devices. In some cases, a digital signal may be communicated by way of one or more communication protocols, including without limitation internet protocol (IP), controller area network (CAN) protocols, serial communication protocols (e.g., universal asynchronous receiver-transmitter [UART]), parallel communication protocols (e.g., IEEE 228 [printer port]), and the like.

Still referring to FIG. 2 , in some cases, a node of system 200 may perform one or more signal processing steps on a sensed characteristic. For instance, a node may analyze, modify, and/or synthesize a signal representative of characteristic in order to improve the signal, for instance by improving transmission, storage efficiency, or signal to noise ratio. Exemplary methods of signal processing may include analog, continuous time, discrete, digital, nonlinear, and statistical. Analog signal processing may be performed on non-digitized or analog signals. Exemplary analog processes may include passive filters, active filters, additive mixers, integrators, delay lines, compandors, multipliers, voltage-controlled filters, voltage-controlled oscillators, and phase-locked loops. Continuous-time signal processing may be used, in some cases, to process signals which varying continuously within a domain, for instance time. Exemplary non-limiting continuous time processes may include time domain processing, frequency domain processing (Fourier transform), and complex frequency domain processing. Discrete time signal processing may be used when a signal is sampled non-continuously or at discrete time intervals (i.e., quantized in time). Analog discrete-time signal processing may process a signal using the following exemplary circuits sample and hold circuits, analog time-division multiplexers, analog delay lines and analog feedback shift registers. Digital signal processing may be used to process digitized discrete-time sampled signals. Commonly, digital signal processing may be performed by a computing device or other specialized digital circuits, such as without limitation an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a specialized digital signal processor (DSP). Digital signal processing may be used to perform any combination of typical arithmetical operations, including fixed-point and floating-point, real-valued and complex-valued, multiplication and addition. Digital signal processing may additionally operate circular buffers and lookup tables. Further non-limiting examples of algorithms that may be performed according to digital signal processing techniques include fast Fourier transform (FFT), finite impulse response (FIR) filter, infinite impulse response (IIR) filter, and adaptive filters such as the Wiener and Kalman filters. Statistical signal processing may be used to process a signal as a random function (i.e., a stochastic process), utilizing statistical properties. For instance, in some embodiments, a signal may be modeled with a probability distribution indicating noise, which then may be used to reduce noise in a processed signal.

Referring now to FIG. 3 , an embodiment of recorder database 300 is illustrated. Recorder database 300 may include any data structure for ordered storage and retrieval of data, which may be implemented as a hardware or software module. Recorder database 300 may be implemented, without limitation, as a relational database, a key-value retrieval datastore such as a NOSQL database, or any other format or structure for use as a datastore that a person skilled in the art would recognize as suitable upon review of the entirety of this disclosure. Recorder database 300 may include a plurality of data entries and/or records corresponding to elements as described above. Data entries and/or records may describe, without limitation, data concerning a vehicle data, a vehicle collection datum, a vehicle model output, and a timetable restriction.

Still referring to FIG. 3 , one or more database tables in recorder database 300 may include, as a non-limiting example, vehicle data table 304. Vehicle data table 304 may be a table storing each vehicle data of the plurality of vehicle data. For instance, and without limitation, recorder database 300 may include vehicle data table 304 listing each vehicle data of the plurality of vehicle data, the associated data of each vehicle data, such as an input datum, a sensor datum, a flight datum, and the like.

Continuing to refer to FIG. 3 , one or more database tables in recorder database 300 may include, as a non-limiting example, vehicle model output table 308. Vehicle model output table 308 may be a table storing the vehicle model output received by at least a vehicle simulator. For instance, and without limitation, recorder database 300 may include vehicle model output table 308 listing a plurality of individual vehicle model outputs, such as vehicle model outputs of the aircraft at different moments in time in the air continuously measured during the duration of a flight.

Continuing to refer to FIG. 3 , one or more database tables in recorder database 300 may include, as a non-limiting example, vehicle collection datum table 312. Vehicle collection datum table 312 may be a table storing the vehicle collection datum from a computing device. For instance, and without limitation, recorder database 300 may include vehicle collection datum table 312 listing a plurality of subsets of a vehicle collection datum continuously measured during the duration of a flight.

Referring now to FIG. 4 , an embodiment of authentication module 132, as pictured in FIG. 1 , is illustrated in detail. Authentication module 132 may include any suitable hardware and/or software module. Authentication module 132 and/or computing device 112 can be configured to authenticate user device 424. Authenticating, for example and without limitation, can include determining a user's ability/authorization to access information included in each module and/or engine of the plurality of modules and/or engines operating on computing device 112. As a further example and without limitation, authentication may include determining an instructor's authorization/ability of access to the information included in each module and/or engine of the plurality of modules and/or engines operating on computing device 112. As a further non-limiting example, authentication may include determining an administrator's authorization/ability to access the information included in each module and/or engine of the plurality of modules and/or engines operating on computing device 112. Authentication may enable access to an individual module and/or engine, a combination of modules and/or engines, and/or all the modules and/or engines operating on computing device 112. Authenticating user device 424 is configured to receive credential 400 from user device 424. Credential 400 may include any credential as described herein. For example and without limitation, credential 400 may include a username and password unique to the user and/or user device 424. As a further example and without limitation, credential 400 may include a PKI certificate unique to the user and/or user device 424. As a further embodiment, credential 400 may be received from instructor device 416 and/or admin device 420, such that credential 400 would authenticate each instructor device 416 and admin device 420, respectively.

Continuing to refer to FIG. 4 , authentication module 132 and/or computing device 112 may be further designed and configured to compare credential 400 from user device 424 to an authorized credential stored in authentication database 404. For example, authentication module 132 and/or computing device 112 may be configured to compare credential 400 from user device 424 to a stored authorized credential to determine if credential 400 matches the stored authorized credential. As a further embodiment, authentication module 132 and/or computing device may compare credential 400 from instructor device 416 to an authorized credential stored in authentication database 404. For example, authentication module 132 and/or computing device may be configured to compare credential 400 from instructor device 416 to a stored authorized credential to determine if credential 400 matches the stored authorized credential. As a further non-limiting example, authentication module 132 and/or computing device may match credential 400 from admin device 420 to an authorized credential stored in authentication database 404. For example, authentication module 132 and/or computing device may be configured to compare credential 400 from admin device 420 to a stored authorized credential to determine if credential 400 matches the stored authorized credential. In embodiments, comparing credential 400 to an authorized credential stored in authentication database 404 can include identifying an authorized credential stored in authentication database 404 by matching credential 400 to at least one authorized credential stored in authentication database 404. Authentication module 132 and/or computing device may include or communicate with authentication database 404. Authentication database 404 may be implemented as any database and/or datastore suitable for use as authentication database 404 as described in the entirety of this disclosure. The “authorized credential” as described in the entirety of this disclosure, is the unique identifier that will successfully authorize each user and/or user device 424 if received. For example and without limitation, the authorized credential is the correct alpha-numeric spelling, letter case, and special characters of the username and password for user device 424. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of various examples of authorized credentials that may be stored in the authentication database consistently with this disclosure.

Still referring to FIG. 4 , authentication module 132 and/or computing device 112 is further designed and configured to bypass authentication for user device 424 based on the identification of the authorized credential stored within authentication database 404. Bypassing authentication may include permitting access to user device 424 to access the information included in each module and/or engine of the plurality of modules and/or engines operating on computing device 112. Bypassing authentication may enable access to an individual module and/or engine, a combination of modules and/or engines, and/or all the modules and/or engines operating on computing device 112, as described in further detail in the entirety of this disclosure. As a further example and without limitation, bypassing authentication may include bypassing authentication for instructor device 416 based on the comparison of the authorized credential stored in authentication database 404. As a further non-limiting example, bypassing authentication may include bypassing authentication for admin device 420 based on the comparison of the authorized credential stored in authentication database 448.

With continued reference to FIG. 4 , authentication module 132 and/or computing device 112 may be further configured to biometrically authenticate user device 424. Biometric authentication, for example and without limitation, determines a user's ability to access the information included in each module and/or engine of the plurality of modules and/or engines operating on computing device 112 as a function of a biometric credential 408. Biometric authentication, in the embodiment, includes receiving biometric credential 408 from user device 424, comparing and/or matching biometric credential 408 from user device 424 to an authorized biometric credential stored in a biometric database 412, and bypassing authentication for user device 424 based on the comparison of the authorized biometric credential stored within biometric database 412. Biometric authentication employing authentication module 132 may also include biometrically authenticating instructor device 416 and/or admin device 420. Authentication module 132 and/or computing device 112 may include or communicate with biometric database 412. Biometric database 412 may be implemented as any database and/or datastore suitable for use as a biometric database entirely with this disclosure. The “biometric credential” as used in this disclosure, is any body measurement and/or calculation utilized for identification purposes, such as a physiological characteristic and/or behavioral characteristic. For example and without limitation, biometric credential 408 may include fingerprints, palm veins, face recognition, DNA, palm print, hand geometry, iris recognition, retina, odor/scent, typing rhythm, gait, voice, and the like. The “authorized biometric credential” as described in the entirety of this disclosure, is unique biometric identifier that will successfully authorize each user and/or user device 424, such that the authorized biometric credential is the correct biometric credential which will enable the user and/or user device 424 access to the plurality of modules and/or engines operating on computing device 112. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of various examples of biometric credentials and authorized biometric credentials that may be utilized by authentication module 132 consistently with this disclosure.

Referring now to FIG. 5 , an embodiment of authentication database 404 is illustrated. Authentication database 404 may include any data structure for ordered storage and retrieval of data, which may be implemented as a hardware or software module. Authentication database 404 may be implemented, without limitation, as a relational database, a key-value retrieval datastore such as a NOSQL database, or any other format or structure for use as a datastore that a person skilled in the art would recognize as suitable upon review of the entirety of this disclosure. Authorization database 404 may include a plurality of data entries and/or records corresponding to credentials as described above. Data entries and/or records may describe, without limitation, data concerning authorized credential datum and failed credential datum.

With continued reference to FIG. 5 , one or more database tables in authentication database 404 may include as a non-limiting example an authorized credential datum table 500. Authorized credential datum table 500 may be a table storing authorized credentials, wherein the authorized credentials may be for user device 424, instruction device 416 and/or admin device 420, as described in further detail in the entirety of this disclosure. For instance, and without limitation, authentication database 404 may include an authorized credential datum table 500 listing unique identifiers stored for user device 424, wherein the authorized credential is compared/matched to a credential 200 received from user device 424.

Still referring to FIG. 5 , one or more database tables in authentication database 404 may include, as a non-limiting example, failed credential datum table 504. A “failed credential”, as described in the entirety of this disclosure, is a credential received from a device that did not match an authorized credential stored within authorized credential datum table 500 of authentication database 404. Such credentials can be received from user device 424, instruction device 416 and/or admin device 420. Failed credential datum table 504 may be a table storing and/or matching failed credentials. For instance and without limitation, authentication database 404 may include failed credential datum table 504 listing incorrect unique identifiers received by a device in authentication module 108, wherein authentication of the device did not result. Tables presented above are presented for exemplary purposes only; persons skilled in the art will be aware of various ways in which data may be organized in authentication database 404 consistently with this disclosure.

Referring now to FIG. 6 , an embodiment of biometric database 412 is illustrated. Biometric database 412 may include any data structure for ordered storage and retrieval of data, which may be implemented as a hardware or software module. Biometric database 412 may be implemented, without limitation, as a relational database, a key-value retrieval datastore such as a NOSQL database, or any other format or structure for use as a datastore that a person skilled in the art would recognize as suitable upon review of the entirety of this disclosure. Biometric database 412 may include a plurality of data entries and/or records corresponding to elements of biometric datum as described above. Data entries and/or records may describe, without limitation, data concerning particular physiological characteristics and/or behavioral characteristics that have been collected. Data entries in a biometric database 412 may be flagged with or linked to one or more additional elements of information, which may be reflected in data entry cells and/or in linked tables such as tables related by one or more indices in a relational database; one or more additional elements of information may include data associating a biometric with one or more cohorts, including demographic groupings such as ethnicity, sex, age, income, geographical region, or the like. Additional elements of information may include one or more categories of biometric datum as described above. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of various ways in which data entries in a biometric database 412 may reflect categories, cohorts, and/or populations of data consistently with this disclosure.

Still referring to FIG. 6 , one or more database tables in biometric database 412 may include, as a non-limiting example, fingerprint data table 600. Fingerprint data table 600 may be a table correlating, relating, and/or matching biometric credentials received from a device, such as user device 424, instructor device 416 and admin device 420, as described above, to fingerprint data. For instance, and without limitation, biometric database 412 may include a fingerprint data table 600 listing samples acquired from a user having allowed system 100 to retrieve fingerprint data from user device 424 through a fingerprint scanner, including biometric scanners such as optical scanners or capacitive scanners, one or more rows recording such an entry may be inserted in fingerprint data table 600.

With continued reference to FIG. 6 , biometric database 412 may include tables listing one or more samples according to a sample source. For instance, and without limitation, biometric database 412 may include typing rhythm database 604 listing samples acquired from a user by obtaining the user's keystroke dynamics when typing characters on a keyboard and/or keypad, such as the time to get to and depress a key, duration the key is held down, use of caps-lock, pace of typing characters, misspellings, or the like. As another non-limiting example, biometric database 412 may include face recognition data table 608, which may list samples acquired from a user associated with user device 424 that has allowed system 100 to obtain digital images or video frames of the user's facial demographics, such as relative position, size, and/or shape of the eyes, nose, cheekbones, jaw, and/or the like. As a further non-limiting example, biometric database 412 may include a voice recognition data table 612, which may list samples acquired from a user associated with user device 424 that has allowed system 100 to retrieve the user's unique voice patterns though a microphone located on user device 424, such as dictation variants, common phrases, volume level, dialect, pitch, format frequencies, and/or the like. As a further example, also non-limiting, biometric database 412 may include iris scan data table 616, which may list samples acquired from a user associated with user device 424 that has allowed system 100 to retrieve a user's iris scan from a camera located on user device 424, including without limitation images of the detailed structures of the iris which are visible externally. As another non-limiting example, biometric database 412 may include retinal scan data table 620, which may include samples acquired from a user associated with user device 424 that has allowed system 100 to extract a user's retinal scan; retinal scans may include an image of the complex and unique structure of an individual's capillaries in the retina. Tables presented above are presented for exemplary purposes only; persons skilled in the art will be aware of various ways in which data may be organized in biometric database 412 consistently with this disclosure.

Referring to FIG. 7 , an avionic mesh network 700 is schematically illustrated. According to some embodiments, an avionic mesh network may include a single network. Alternatively or additionally, an avionic mesh network may include more than a single network. A single networks may be differentiated according to address, for example Internet Protocol address, gateway, or name server used. For example, in some cases, multiple networks may use different gateways, even though the multiple networks may still be within communicative connection with one another.

With continued reference to FIG. 7 , in some embodiments, an avionic mesh network 700 may include inter-aircraft network nodes, intra-aircraft network nodes, as well as non-aircraft network nodes. As used in this disclosure, a “network node” is any component communicatively coupled to at least a network. For example, a network node may include an endpoint, for example a computing device on network, a switch, a router, a bridge, and the like. A network node may include a redistribution point, for example a switch, or an endpoint, for example a component communicatively connected to network. As used in this disclosure, “inter-aircraft network nodes” are two or more network nodes that are physically located in two or more aircraft and communicatively connected by way of an inter-aircraft network. As used in this disclosure, “intra-aircraft network nodes” are two or more intra-aircraft network nodes that are each physically located within a single aircraft and communicatively connected. As used in this disclosure, a “non-aircraft network node” is a network node that is not located on an aircraft and is communicatively connected to a network.

With continued reference to FIG. 7 , in some embodiments, avionic mesh network 700 may include a wireless mesh network organized in a mesh topology. A mesh topology may include a networked infrastructure in which network nodes may be connected directly, dynamically, and/or non-hierarchically to many other nodes (e.g., as many other nodes as possible). In some cases, a mesh topology may be configured to facilitate cooperation between network nodes, for example redistributive network nodes, in routing of communication between network participants (e.g., other network nodes). A mesh topology may facilitate a lack of dependency on any given node, thereby allowing other nodes to participate in relaying communication. In some cases, mesh networks may dynamically self-organize and self-configure. Self-configuration enables dynamic distribution of workloads, particularly in event a network node failure, thereby contributing to fault-tolerance and reduced maintenance requirements. In some embodiments, mesh networks can relay messages using either a flooding technique or a routing technique. A flooding technique sends a message to every network node, flooding network with the message. A routing technique allows a mesh network to communicate a message is propagated along a determined nodal path to the message's intended destination. Message routing may be performed by mesh networks in part by ensuring that all nodal paths are available. Nodal path availability may be ensured by maintaining continuous nodal network connections and reconfiguring nodal paths with an occurrence of broken nodal paths. Reconfiguration of nodal paths, in some cases, may be performed by utilizing self-healing algorithms, such as without limitation Shortest Path Bridging. Self-healing allows a routing-based network to operate when a node fails or when a connection becomes unreliable. In some embodiments, a mesh network having all network nodes connected to each other may be termed a fully connected network. Fully connected wired networks have advantages of security and reliability. For example, an unreliable wired connection between two wired network nodes will only affect only two nodes attached to the unreliable wired connection.

With continued reference to FIG. 7 , an exemplary avionic mesh network 700 is shown providing communicative connection between a computing device 704 and aircraft 708A-C. Computing device 704 may include any computing device described in this disclosure. In some embodiments, computing device 704 may be connected to a terrestrial network 712. Terrestrial networks 712 may include any network described in this disclosure and may include, without limitation, wireless networks, local area networks (LANs), wide area networks (WANs), ethernet, Internet, mobile broadband, fiber optic communication, and the like. In some cases, a grounded aircraft 708C may be connected to an avionic mesh network 700 by way of a terrestrial network 712. In some cases, avionic mesh network 700 may include a wireless communication node 716. A wireless communication node 716 may provide communicative connection by way of wireless networking. Wireless networking may include any wireless network method described in this disclosure, including without limitation Wi-Fi, mobile broadband, optical communication, radio communication, and the like. In some cases, wireless communication node 716 may be configured to connect with a first airborne aircraft in flight 708A. First airborne aircraft in some embodiments may include at least a first intra-aircraft network node 720A. As described above, first intra-aircraft network node 720A may be configured to connect to other nodes within first airborne aircraft 708A. In some cases, avionic mesh network 700 may be configured to provide inter-aircraft communication, for instance by using a first inter-aircraft network node 724A. In some cases, first inter-aircraft network node may be configured to communicate with a second inter-aircraft network node 724B. Inter-aircraft nodes 720A-B may include radio communication and/or optical wireless communication, for example free space optical communication.

With continued reference to FIG. 7 , avionic mesh network 700 may be additionally configured to provide for encrypted and/or secured communication between components, i.e., nodes, communicative on the network. In some cases, encrypted communication on network 700 may be provided for by way of end-to-end encryption. Exemplary non-limited end-to-end encryption methods include symmetric key encryption, asymmetric key encryption, public key encryption methods, private key encryption methods and the like. In some cases, avionic mesh network 700 and/or another network may be configured to provide secure key exchange for encryption methods. Exemplary non-limiting key exchange methods include Diffie-Hellman key exchange, Supersingular isogeny key exchange, use of at least a trusted key authority, password authenticated key agreement, forward secrecy, quantum key exchange, and the like. In some cases, an avionic mesh network 700 may include at least an optical network component, for example fiber optic cables, wireless optical networks, and/or free space optical network. In some cases, encrypted communication between network nodes may be implemented by way of optical network components. For example, quantum key exchange in some embodiments, may defeat man-in-the-middle attacks. This is generally because, observation of a quantum system disturbs the quantum system. Quantum key exchange in some cases, uses this general characteristic of quantum physics to communicate sensitive information, such as an encryption key, by encoding the sensitive information in polarization state of quantum of radiation. At least a polarization sensitive detector may be used to decode sensitive information.

Still referring to FIG. 7 , in an embodiment, methods and systems described herein may perform or implement one or more aspects of a cryptographic system. In one embodiment, a cryptographic system is a system that converts data from a first form, known as “plaintext,” which is intelligible when viewed in its intended format, into a second form, known as “ciphertext,” which is not intelligible when viewed in the same way. Ciphertext may be unintelligible in any format unless first converted back to plaintext. In one embodiment, a process of converting plaintext into ciphertext is known as “encryption.” Encryption process may involve the use of a datum, known as an “encryption key,” to alter plaintext. Cryptographic system may also convert ciphertext back into plaintext, which is a process known as “decryption.” Decryption process may involve the use of a datum, known as a “decryption key,” to return the ciphertext to its original plaintext form. In embodiments of cryptographic systems that are “symmetric,” decryption key is essentially the same as encryption key: possession of either key makes it possible to deduce the other key quickly without further secret knowledge. Encryption and decryption keys in symmetric cryptographic systems may be kept secret and shared only with persons or entities that the user of the cryptographic system wishes to be able to decrypt the ciphertext. One example of a symmetric cryptographic system is the Advanced Encryption Standard (“AES”), which arranges plaintext into matrices and then modifies the matrices through repeated permutations and arithmetic operations with an encryption key.

Still referring to FIG. 7 , in embodiments of cryptographic systems that are “asymmetric,” either encryption or decryption key cannot be readily deduced without additional secret knowledge, even given the possession of a corresponding decryption or encryption key, respectively; a common example is a “public key cryptographic system,” in which possession of the encryption key does not make it practically feasible to deduce the decryption key, so that the encryption key may safely be made available to the public. An example of a public key cryptographic system is RSA, in which an encryption key involves the use of numbers that are products of very large prime numbers, but a decryption key involves the use of those very large prime numbers, such that deducing the decryption key from the encryption key requires the practically infeasible task of computing the prime factors of a number which is the product of two very large prime numbers. Another example is elliptic curve cryptography, which relies on the fact that given two points P and Q on an elliptic curve over a finite field, and a definition for addition where A+B=−R, the point where a line connecting point A and point B intersects the elliptic curve, where “0,” the identity, is a point at infinity in a projective plane containing the elliptic curve, finding a number k such that adding P to itself k times results in Q is computationally impractical, given correctly selected elliptic curve, finite field, and P and Q.

With continued reference to FIG. 7 , in some cases, avionic mesh network 700 may be configured to allow message authentication between network nodes. In some cases, message authentication may include a property that a message has not been modified while in transit and that receiving party can verify source of the message. In some embodiments, message authentication may include us of message authentication codes (MACs), authenticated encryption (AE), and/or digital signature. Message authentication code, also known as digital authenticator, may be used as an integrity check based on a secret key shared by two parties to authenticate information transmitted between them. In some cases, a digital authenticator may use a cryptographic hash and/or an encryption algorithm.

Still referring to FIG. 7 , in some embodiments, systems and methods described herein produce cryptographic hashes, also referred to by the equivalent shorthand term “hashes.” A cryptographic hash, as used herein, is a mathematical representation of a lot of data, such as files or blocks in a block chain as described in further detail below; the mathematical representation is produced by a lossy “one-way” algorithm known as a “hashing algorithm.” Hashing algorithm may be a repeatable process; that is, identical lots of data may produce identical hashes each time they are subjected to a particular hashing algorithm. Because hashing algorithm is a one-way function, it may be impossible to reconstruct a lot of data from a hash produced from the lot of data using the hashing algorithm. In the case of some hashing algorithms, reconstructing the full lot of data from the corresponding hash using a partial set of data from the full lot of data may be possible only by repeatedly guessing at the remaining data and repeating the hashing algorithm; it is thus computationally difficult if not infeasible for a single computer to produce the lot of data, as the statistical likelihood of correctly guessing the missing data may be extremely low. However, the statistical likelihood of a computer of a set of computers simultaneously attempting to guess the missing data within a useful timeframe may be higher, permitting mining protocols as described in further detail below.

Still referring to FIG. 7 , in an embodiment, hashing algorithm may demonstrate an “avalanche effect,” whereby even extremely small changes to lot of data produce drastically different hashes. This may thwart attempts to avoid the computational work necessary to recreate a hash by simply inserting a fraudulent datum in data lot, enabling the use of hashing algorithms for “tamper-proofing” data such as data contained in an immutable ledger as described in further detail below. This avalanche or “cascade” effect may be evinced by various hashing processes; persons skilled in the art, upon reading the entirety of this disclosure, will be aware of various suitable hashing algorithms for purposes described herein. Verification of a hash corresponding to a lot of data may be performed by running the lot of data through a hashing algorithm used to produce the hash. Such verification may be computationally expensive, albeit feasible, potentially adding up to significant processing delays where repeated hashing, or hashing of large quantities of data, is required, for instance as described in further detail below. Examples of hashing programs include, without limitation, SHA256, a NIST standard; further current and past hashing algorithms include Winternitz hashing algorithms, various generations of Secure Hash Algorithm (including “SHA-1,” “SHA-2,” and “SHA-3”), “Message Digest” family hashes such as “MD4,” “MD5,” “MD6,” and “RIPEMD,” Keccak, “BLAKE” hashes and progeny (e.g., “BLAKE2,” “BLAKE-256,” “BLAKE-512,” and the like), Message Authentication Code (“MAC”)-family hash functions such as PMAC, OMAC, VMAC, HMAC, and UMAC, Poly1305-AES, Elliptic Curve Only Hash (“ECOH”) and similar hash functions, Fast-Syndrome-based (FSB) hash functions, GOST hash functions, the Grøstl hash function, the HAS-160 hash function, the JH hash function, the RadioGatún hash function, the Skein hash function, the Streebog hash function, the SWIFFT hash function, the Tiger hash function, the Whirlpool hash function, or any hash function that satisfies, at the time of implementation, the requirements that a cryptographic hash be deterministic, infeasible to reverse-hash, infeasible to find collisions, and have the property that small changes to an original message to be hashed will change the resulting hash so extensively that the original hash and the new hash appear uncorrelated to each other. A degree of security of a hash function in practice may depend both on the hash function itself and on characteristics of the message and/or digest used in the hash function. For example, where a message is random, for a hash function that fulfills collision-resistance requirements, a brute-force or “birthday attack” may to detect collision may be on the order of O(2^(n/2)) for n output bits; thus, it may take on the order of 2²⁵⁶ operations to locate a collision in a 512 bit output “Dictionary” attacks on hashes likely to have been generated from a non-random original text can have a lower computational complexity, because the space of entries they are guessing is far smaller than the space containing all random permutations of bits. However, the space of possible messages may be augmented by increasing the length or potential length of a possible message, or by implementing a protocol whereby one or more randomly selected strings or sets of data are added to the message, rendering a dictionary attack significantly less effective.

Continuing to refer to FIG. 7 , a “secure proof,” as used in this disclosure, is a protocol whereby an output is generated that demonstrates possession of a secret, such as device-specific secret, without demonstrating the entirety of the device-specific secret; in other words, a secure proof by itself, is insufficient to reconstruct the entire device-specific secret, enabling the production of at least another secure proof using at least a device-specific secret. A secure proof may be referred to as a “proof of possession” or “proof of knowledge” of a secret. Where at least a device-specific secret is a plurality of secrets, such as a plurality of challenge-response pairs, a secure proof may include an output that reveals the entirety of one of the plurality of secrets, but not all of the plurality of secrets; for instance, secure proof may be a response contained in one challenge-response pair. In an embodiment, proof may not be secure; in other words, proof may include a one-time revelation of at least a device-specific secret, for instance as used in a single challenge-response exchange.

Still referring to FIG. 7 , secure proof may include a zero-knowledge proof, which may provide an output demonstrating possession of a secret while revealing none of the secret to a recipient of the output; zero-knowledge proof may be information-theoretically secure, meaning that an entity with infinite computing power would be unable to determine secret from output. Alternatively, zero-knowledge proof may be computationally secure, meaning that determination of secret from output is computationally infeasible, for instance to the same extent that determination of a private key from a public key in a public key cryptographic system is computationally infeasible. Zero-knowledge proof algorithms may generally include a set of two algorithms, a prover algorithm, or “P,” which is used to prove computational integrity and/or possession of a secret, and a verifier algorithm, or “V” whereby a party may check the validity of P. Zero-knowledge proof may include an interactive zero-knowledge proof, wherein a party verifying the proof must directly interact with the proving party; for instance, the verifying and proving parties may be required to be online, or connected to the same network as each other, at the same time. Interactive zero-knowledge proof may include a “proof of knowledge” proof, such as a Schnorr algorithm for proof on knowledge of a discrete logarithm. in a Schnorr algorithm, a prover commits to a randomness r, generates a message based on r, and generates a message adding r to a challenge c multiplied by a discrete logarithm that the prover is able to calculate; verification is performed by the verifier who produced c by exponentiation, thus checking the validity of the discrete logarithm. Interactive zero-knowledge proofs may alternatively or additionally include sigma protocols. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of various alternative interactive zero-knowledge proofs that may be implemented consistently with this disclosure.

Still referring to FIG. 7 , alternatively, zero-knowledge proof may include a non-interactive zero-knowledge, proof, or a proof wherein neither party to the proof interacts with the other party to the proof; for instance, each of a party receiving the proof and a party providing the proof may receive a reference datum which the party providing the proof may modify or otherwise use to perform the proof. As a non-limiting example, zero-knowledge proof may include a succinct non-interactive arguments of knowledge (ZK-SNARKS) proof, wherein a “trusted setup” process creates proof and verification keys using secret (and subsequently discarded) information encoded using a public key cryptographic system, a prover runs a proving algorithm using the proving key and secret information available to the prover, and a verifier checks the proof using the verification key; public key cryptographic system may include RSA, elliptic curve cryptography, ElGamal, or any other suitable public key cryptographic system. Generation of trusted setup may be performed using a secure multiparty computation so that no one party has control of the totality of the secret information used in the trusted setup; as a result, if any one party generating the trusted setup is trustworthy, the secret information may be unrecoverable by malicious parties. As another non-limiting example, non-interactive zero-knowledge proof may include a Succinct Transparent Arguments of Knowledge (ZK-STARKS) zero-knowledge proof. In an embodiment, a ZK-STARKS proof includes a Merkle root of a Merkle tree representing evaluation of a secret computation at some number of points, which may be 1 billion points, plus Merkle branches representing evaluations at a set of randomly selected points of the number of points; verification may include determining that Merkle branches provided match the Merkle root, and that point verifications at those branches represent valid values, where validity is shown by demonstrating that all values belong to the same polynomial created by transforming the secret computation. In an embodiment, ZK-STARKS does not require a trusted setup.

Still referring to FIG. 7 , zero-knowledge proof may include any other suitable zero-knowledge proof. Zero-knowledge proof may include, without limitation bulletproofs. Zero-knowledge proof may include a homomorphic public-key cryptography (hPKC)-based proof. Zero-knowledge proof may include a discrete logarithmic problem (DLP) proof. Zero-knowledge proof may include a secure multi-party computation (MPC) proof. Zero-knowledge proof may include, without limitation, an incrementally verifiable computation (IVC). Zero-knowledge proof may include an interactive oracle proof (IOP). Zero-knowledge proof may include a proof based on the probabilistically checkable proof (PCP) theorem, including a linear PCP (LPCP) proof. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of various forms of zero-knowledge proofs that may be used, singly or in combination, consistently with this disclosure.

Still referring to FIG. 7 , in an embodiment, secure proof is implemented using a challenge-response protocol. In an embodiment, this may function as a one-time pad implementation; for instance, a manufacturer or other trusted party may record a series of outputs (“responses”) produced by a device possessing secret information, given a series of corresponding inputs (“challenges”), and store them securely. In an embodiment, a challenge-response protocol may be combined with key generation. A single key may be used in one or more digital signatures as described in further detail below, such as signatures used to receive and/or transfer possession of crypto-currency assets; the key may be discarded for future use after a set period of time. In an embodiment, varied inputs include variations in local physical parameters, such as fluctuations in local electromagnetic fields, radiation, temperature, and the like, such that an almost limitless variety of private keys may be so generated. Secure proof may include encryption of a challenge to produce the response, indicating possession of a secret key. Encryption may be performed using a private key of a public key cryptographic system, or using a private key of a symmetric cryptographic system; for instance, trusted party may verify response by decrypting an encryption of challenge or of another datum using either a symmetric or public-key cryptographic system, verifying that a stored key matches the key used for encryption as a function of at least a device-specific secret. Keys may be generated by random variation in selection of prime numbers, for instance for the purposes of a cryptographic system such as RSA that relies prime factoring difficulty. Keys may be generated by randomized selection of parameters for a seed in a cryptographic system, such as elliptic curve cryptography, which is generated from a seed. Keys may be used to generate exponents for a cryptographic system such as Diffie-Helman or ElGamal that are based on the discrete logarithm problem.

Still referring to FIG. 7 , as described above in some embodiments an avionic mesh network 700 may provide secure and/or encrypted communication at least in part by employing digital signatures. A “digital signature,” as used herein, includes a secure proof of possession of a secret by a signing device, as performed on provided element of data, known as a “message.” A message may include an encrypted mathematical representation of a file or other set of data using the private key of a public key cryptographic system. Secure proof may include any form of secure proof as described above, including without limitation encryption using a private key of a public key cryptographic system as described above. Signature may be verified using a verification datum suitable for verification of a secure proof; for instance, where secure proof is enacted by encrypting message using a private key of a public key cryptographic system, verification may include decrypting the encrypted message using the corresponding public key and comparing the decrypted representation to a purported match that was not encrypted; if the signature protocol is well-designed and implemented correctly, this means the ability to create the digital signature is equivalent to possession of the private decryption key and/or device-specific secret. Likewise, if a message making up a mathematical representation of file is well-designed and implemented correctly, any alteration of the file may result in a mismatch with the digital signature; the mathematical representation may be produced using an alteration-sensitive, reliably reproducible algorithm, such as a hashing algorithm as described above. A mathematical representation to which the signature may be compared may be included with signature, for verification purposes; in other embodiments, the algorithm used to produce the mathematical representation may be publicly available, permitting the easy reproduction of the mathematical representation corresponding to any file.

Still viewing FIG. 7 , in some embodiments, digital signatures may be combined with or incorporated in digital certificates. In one embodiment, a digital certificate is a file that conveys information and links the conveyed information to a “certificate authority” that is the issuer of a public key in a public key cryptographic system. Certificate authority in some embodiments contains data conveying the certificate authority's authorization for the recipient to perform a task. The authorization may be the authorization to access a given datum. The authorization may be the authorization to access a given process. In some embodiments, the certificate may identify the certificate authority. The digital certificate may include a digital signature.

With continued reference to FIG. 7 , in some embodiments, a third party such as a certificate authority (CA) is available to verify that the possessor of the private key is a particular entity; thus, if the certificate authority may be trusted, and the private key has not been stolen, the ability of an entity to produce a digital signature confirms the identity of the entity and links the file to the entity in a verifiable way. Digital signature may be incorporated in a digital certificate, which is a document authenticating the entity possessing the private key by authority of the issuing certificate authority and signed with a digital signature created with that private key and a mathematical representation of the remainder of the certificate. In other embodiments, digital signature is verified by comparing the digital signature to one known to have been created by the entity that purportedly signed the digital signature; for instance, if the public key that decrypts the known signature also decrypts the digital signature, the digital signature may be considered verified. Digital signature may also be used to verify that the file has not been altered since the formation of the digital signature.

Referring now to FIG. 8 , a flow diagram of an exemplary method 800 for transmitting and storing data based on connection for a vehicle is provided. Method 800, at step 805, may include receiving, by a computing device, a vehicle data. Computing device may include any computing device as described herein. Vehicle may include an aircraft such as an electric aircraft. Vehicle data may include any vehicle data as described herein. Step 805 may include, wherein receiving at least an input datum and at least a sensor datum. At least the input datum may include any input datum as described herein. At least the sensor datum may include any sensor datum as described herein. In a non-limiting embodiment, method 800 may include detecting, by a sensor, the vehicle data and transmitting the vehicle data to the computing device. The sensor may include any sensor as described herein. In a non-limiting embodiment, method 800 may include transmitting the vehicle data to computing device as a function of a plurality of physical controller area network (CAN) buses communicatively connected to the aircraft. A physical CAN bus may include any physical CAN bus as described herein.

With continued reference to FIG. 8 , method 800, at step 810, includes generating a vehicle collection datum as a function of the vehicle data. The vehicle collection datum may include any vehicle collection datum as described herein. Step 810 may include generating a vehicle model output as a function of a vehicle simulator. The vehicle simulator may include any vehicle simulator as described herein. The vehicle model output may include any vehicle model output as described herein. In a non-limiting embodiment, step 810 may include determining a subset of received vehicle data from the vehicle collection datum to store, wherein the subset further comprises a plurality of vehicle model outputs. The subset may include any subset as described herein. In a non-limiting embodiment, step 810 may include generating the vehicle collection datum as a function of a machine-learning algorithm. In a non-limiting embodiment, step 820 may include, selecting a training set as a function each measured vehicle data and vehicle model output wherein the training set includes each vehicle collection data of a plurality of vehicle collection data correlated to an element of vehicle model data, generating, using a supervised machine-learning algorithm, the vehicle collection datum based on the vehicle data and the selected training set, the vehicle collection datum including each vehicle collection data of the plurality of vehicle collection data for each measured vehicle data of the plurality of measure vehicle data and recording each vehicle collection data of the plurality of vehicle collection data in the recorder database. The recorder database may include any recorder database as described herein

With continued reference to FIG. 8 , method 800, at step 815, includes determining that the computing device is not currently connected to a network. In a non-limiting embodiment, step 815, may include determining that the computing device is connected to a network. The network may include any network as described herein. In a non-limiting embodiment, step 815 may include determining the computing device is not connected to any connection such as a Bluetooth connection with another device such as another aircraft in the air, another remote device, and the like thereof.

With continued reference to FIG. 8 , method 800, at step 820, includes storing the vehicle collection datum in a recorder database as a function of a lack of identification of the mesh network. In a non-limiting embodiment, step 820 may include initiating a timer to count how long the computing device has not found or established a connection in which the computing device may then store any vehicle collection datum and/or remaining vehicle collection datum into the recorder database. In a non-limiting embodiment, step 820 may include storing, by the computing device, the vehicle data in the recorder database, storing the plurality of vehicle model output in the recorder database, storing the vehicle collection datum in the recorder database, and performing at least a database encryption on each datum stored in the recorder database. The database encryption may include any database encryption as described herein

With continued reference to FIG. 8 , method 800, at step 825, includes communicatively connecting the computing device to a second device as a function of a mesh network. The network may include any network as described herein. The mesh network may include any mesh network as described herein. The second device may include any second device as described herein. In a non-limiting embodiment, the second device may include another vehicle and/or aircraft in the sky. In a non-limiting embodiment, step 825 may include the electric aircraft and the computing device automatically detecting a network and open communication with another device while remaining in the radius of the network. In a non-limiting embodiment, step 825 may include the electric aircraft and computing detecting another aircraft in the sky and forming a connection with that other aircraft via any method of wireless connection.

With continued reference to FIG. 8 , method 800, at step 830, includes authenticating the second device as a function of an authentication module. The authentication module may include any authentication module as described herein. Step 830 may include receiving, by the authentication module, a credential from the second device, comparing the credential to an authorized credential stored within an authentication database, and bypassing authentication for the second device based on the comparison of the received credential from the second device to the authorized credential stored within the authentication database. The credential may include any credential as described herein. The authentication database may include any authentication database as described herein.

With continued reference to FIG. 8 , method 800, at step 835, includes communicating the vehicle data to the second device as a function of the mesh network. Communicating may include any communication as described herein. In a non-limiting embodiment, step 835 may include transmitting the vehicle collection datum in subsets of vehicle data as a function of constant time intervals determined by a timer module. The timer module may include any timer module as described herein

Referring now to FIG. 9 , an exemplary embodiment of an aircraft 900, which may include, or be incorporated with, a system for optimization of a recharging flight plan is illustrated. As used in this disclosure an “aircraft” is any vehicle that may fly by gaining support from the air. As a non-limiting example, aircraft may include airplanes, helicopters, commercial and/or recreational aircrafts, instrument flight aircrafts, drones, electric aircrafts, airliners, rotorcrafts, vertical takeoff and landing aircrafts, jets, airships, blimps, gliders, paramotors, and the like thereof.

Still referring to FIG. 9 , aircraft 900 may include an electrically powered aircraft. In embodiments, electrically powered aircraft may be an electric vertical takeoff and landing (eVTOL) aircraft. Aircraft 900 may include an unmanned aerial vehicle and/or a drone. Electric aircraft may be capable of rotor-based cruising flight, rotor-based takeoff, rotor-based landing, fixed-wing cruising flight, airplane-style takeoff, airplane-style landing, and/or any combination thereof. Electric aircraft may include one or more manned and/or unmanned aircrafts. Electric aircraft may include one or more all-electric short takeoff and landing (eSTOL) aircrafts. For example, and without limitation, eSTOL aircrafts may accelerate the plane to a flight speed on takeoff and decelerate the plane after landing. In an embodiment, and without limitation, electric aircraft may be configured with an electric propulsion assembly. Electric propulsion assembly may include any electric propulsion assembly as described in U.S. Nonprovisional application Ser. No. 16/703,225, and entitled “AN INTEGRATED ELECTRIC PROPULSION ASSEMBLY,” the entirety of which is incorporated herein by reference. For purposes of description herein, the terms “upper”, “lower”, “left”, “rear”, “right”, “front”, “vertical”, “horizontal”, “upward”, “downward”, “forward”, “backward” and derivatives thereof shall relate to the invention as oriented in FIG. 9 .

Still referring to FIG. 9 , aircraft 900 includes a fuselage 904. As used in this disclosure a “fuselage” is the main body of an aircraft, or in other words, the entirety of the aircraft except for the cockpit, nose, wings, empennage, nacelles, any and all control surfaces, and generally contains an aircraft's payload. Fuselage 904 may include structural elements that physically support a shape and structure of an aircraft. Structural elements may take a plurality of forms, alone or in combination with other types. Structural elements may vary depending on a construction type of aircraft such as without limitation a fuselage 904. Fuselage 904 may comprise a truss structure. A truss structure may be used with a lightweight aircraft and comprises welded steel tube trusses. A “truss,” as used in this disclosure, is an assembly of beams that create a rigid structure, often in combinations of triangles to create three-dimensional shapes. A truss structure may alternatively comprise wood construction in place of steel tubes, or a combination thereof. In embodiments, structural elements may comprise steel tubes and/or wood beams. In an embodiment, and without limitation, structural elements may include an aircraft skin. Aircraft skin may be layered over the body shape constructed by trusses. Aircraft skin may comprise a plurality of materials such as plywood sheets, aluminum, fiberglass, and/or carbon fiber, the latter of which will be addressed in greater detail later herein.

In embodiments, and with continued reference to FIG. 9 , aircraft fuselage 904 may include and/or be constructed using geodesic construction. Geodesic structural elements may include stringers wound about formers (which may be alternatively called station frames) in opposing spiral directions. A “stringer,” as used in this disclosure, is a general structural element that includes a long, thin, and rigid strip of metal or wood that is mechanically coupled to and spans a distance from, station frame to station frame to create an internal skeleton on which to mechanically couple aircraft skin. A former (or station frame) may include a rigid structural element that is disposed along a length of an interior of aircraft fuselage 904 orthogonal to a longitudinal (nose to tail) axis of the aircraft and may form a general shape of fuselage 904. A former may include differing cross-sectional shapes at differing locations along fuselage 904, as the former is the structural element that informs the overall shape of a fuselage 904 curvature. In embodiments, aircraft skin may be anchored to formers and strings such that the outer mold line of a volume encapsulated by formers and stringers comprises the same shape as aircraft 900 when installed. In other words, former(s) may form a fuselage's ribs, and the stringers may form the interstitials between such ribs. The spiral orientation of stringers about formers may provide uniform robustness at any point on an aircraft fuselage such that if a portion sustains damage, another portion may remain largely unaffected. Aircraft skin may be mechanically coupled to underlying stringers and formers and may interact with a fluid, such as air, to generate lift and perform maneuvers.

In an embodiment, and still referring to FIG. 9 , fuselage 904 may include and/or be constructed using monocoque construction. Monocoque construction may include a primary structure that forms a shell (or skin in an aircraft's case) and supports physical loads. Monocoque fuselages are fuselages in which the aircraft skin or shell is also the primary structure. In monocoque construction aircraft skin would support tensile and compressive loads within itself and true monocoque aircraft can be further characterized by the absence of internal structural elements. Aircraft skin in this construction method is rigid and can sustain its shape with no structural assistance form underlying skeleton-like elements. Monocoque fuselage may comprise aircraft skin made from plywood layered in varying grain directions, epoxy-impregnated fiberglass, carbon fiber, or any combination thereof.

According to embodiments, and further referring to FIG. 9 , fuselage 904 may include a semi-monocoque construction. Semi-monocoque construction, as used herein, is a partial monocoque construction, wherein a monocoque construction is describe above detail. In semi-monocoque construction, aircraft fuselage 904 may derive some structural support from stressed aircraft skin and some structural support from underlying frame structure made of structural elements. Formers or station frames can be seen running transverse to the long axis of fuselage 904 with circular cutouts which are generally used in real-world manufacturing for weight savings and for the routing of electrical harnesses and other modern on-board systems. In a semi-monocoque construction, stringers are thin, long strips of material that run parallel to fuselage's long axis. Stringers may be mechanically coupled to formers permanently, such as with rivets. Aircraft skin may be mechanically coupled to stringers and formers permanently, such as by rivets as well. A person of ordinary skill in the art will appreciate, upon reviewing the entirety of this disclosure, that there are numerous methods for mechanical fastening of the aforementioned components like screws, nails, dowels, pins, anchors, adhesives like glue or epoxy, or bolts and nuts, to name a few. A subset of fuselage under the umbrella of semi-monocoque construction includes unibody vehicles. Unibody, which is short for “unitized body” or alternatively “unitary construction”, vehicles are characterized by a construction in which the body, floor plan, and chassis form a single structure. In the aircraft world, unibody may be characterized by internal structural elements like formers and stringers being constructed in one piece, integral to the aircraft skin as well as any floor construction like a deck.

Still referring to FIG. 9 , stringers and formers, which may account for the bulk of an aircraft structure excluding monocoque construction, may be arranged in a plurality of orientations depending on aircraft operation and materials. Stringers may be arranged to carry axial (tensile or compressive), shear, bending or torsion forces throughout their overall structure. Due to their coupling to aircraft skin, aerodynamic forces exerted on aircraft skin will be transferred to stringers. A location of said stringers greatly informs the type of forces and loads applied to each and every stringer, all of which may be handled by material selection, cross-sectional area, and mechanical coupling methods of each member. A similar assessment may be made for formers. In general, formers may be significantly larger in cross-sectional area and thickness, depending on location, than stringers. Both stringers and formers may comprise aluminum, aluminum alloys, graphite epoxy composite, steel alloys, titanium, or an undisclosed material alone or in combination.

In an embodiment, and still referring to FIG. 9 , stressed skin, when used in semi-monocoque construction is the concept where the skin of an aircraft bears partial, yet significant, load in an overall structural hierarchy. In other words, an internal structure, whether it be a frame of welded tubes, formers and stringers, or some combination, may not be sufficiently strong enough by design to bear all loads. The concept of stressed skin may be applied in monocoque and semi-monocoque construction methods of fuselage 904. Monocoque comprises only structural skin, and in that sense, aircraft skin undergoes stress by applied aerodynamic fluids imparted by the fluid. Stress as used in continuum mechanics may be described in pound-force per square inch (lbf/in²) or Pascals (Pa). In semi-monocoque construction stressed skin may bear part of aerodynamic loads and additionally may impart force on an underlying structure of stringers and formers.

Still referring to FIG. 9 , it should be noted that an illustrative embodiment is presented only, and this disclosure in no way limits the form or construction method of a system and method for loading payload into an eVTOL aircraft. In embodiments, fuselage 904 may be configurable based on the needs of the eVTOL per specific mission or objective. The general arrangement of components, structural elements, and hardware associated with storing and/or moving a payload may be added or removed from fuselage 904 as needed, whether it is stowed manually, automatedly, or removed by personnel altogether. Fuselage 904 may be configurable for a plurality of storage options. Bulkheads and dividers may be installed and uninstalled as needed, as well as longitudinal dividers where necessary. Bulkheads and dividers may be installed using integrated slots and hooks, tabs, boss and channel, or hardware like bolts, nuts, screws, nails, clips, pins, and/or dowels, to name a few. Fuselage 904 may also be configurable to accept certain specific cargo containers, or a receptable that can, in turn, accept certain cargo containers.

Still referring to FIG. 9 , aircraft 900 may include a plurality of laterally extending elements attached to fuselage 904. As used in this disclosure a “laterally extending element” is an element that projects essentially horizontally from fuselage, including an outrigger, a spar, and/or a fixed wing that extends from fuselage. Wings may be structures which include airfoils configured to create a pressure differential resulting in lift. Wings may generally dispose on the left and right sides of the aircraft symmetrically, at a point between nose and empennage. Wings may comprise a plurality of geometries in planform view, swept swing, tapered, variable wing, triangular, oblong, elliptical, square, among others. A wing's cross section geometry may comprise an airfoil. An “airfoil” as used in this disclosure is a shape specifically designed such that a fluid flowing above and below it exert differing levels of pressure against the top and bottom surface. In embodiments, the bottom surface of an aircraft can be configured to generate a greater pressure than does the top, resulting in lift. Laterally extending element may comprise differing and/or similar cross-sectional geometries over its cord length or the length from wing tip to where wing meets the aircraft's body. One or more wings may be symmetrical about the aircraft's longitudinal plane, which comprises the longitudinal or roll axis reaching down the center of the aircraft through the nose and empennage, and the plane's yaw axis. Laterally extending element may comprise controls surfaces configured to be commanded by a pilot or pilots to change a wing's geometry and therefore its interaction with a fluid medium, like air. Control surfaces may comprise flaps, ailerons, tabs, spoilers, and slats, among others. The control surfaces may dispose on the wings in a plurality of locations and arrangements and in embodiments may be disposed at the leading and trailing edges of the wings, and may be configured to deflect up, down, forward, aft, or a combination thereof. An aircraft, including a dual-mode aircraft may comprise a combination of control surfaces to perform maneuvers while flying or on ground.

Still referring to FIG. 9 , aircraft 900 includes a plurality of flight components 908. As used in this disclosure a “flight component” is a component that promotes flight and guidance of an aircraft. In an embodiment, flight component 908 may be mechanically coupled to an aircraft. As used herein, a person of ordinary skill in the art would understand “mechanically coupled” to mean that at least a portion of a device, component, or circuit is connected to at least a portion of the aircraft via a mechanical coupling. Said mechanical coupling can include, for example, rigid coupling, such as beam coupling, bellows coupling, bushed pin coupling, constant velocity, split-muff coupling, diaphragm coupling, disc coupling, donut coupling, elastic coupling, flexible coupling, fluid coupling, gear coupling, grid coupling, hirth joints, hydrodynamic coupling, jaw coupling, magnetic coupling, Oldham coupling, sleeve coupling, tapered shaft lock, twin spring coupling, rag joint coupling, universal joints, or any combination thereof. In an embodiment, mechanical coupling may be used to connect the ends of adjacent parts and/or objects of an electric aircraft. Further, in an embodiment, mechanical coupling may be used to join two pieces of rotating electric aircraft components.

Still referring to FIG. 9 , plurality of flight components 908 may include at least a lift propulsor component 912. As used in this disclosure a “lift propulsor component” is a component and/or device used to propel a craft upward by exerting downward force on a fluid medium, which may include a gaseous medium such as air or a liquid medium such as water. Lift propulsor component 912 may include any device or component that consumes electrical power on demand to propel an electric aircraft in a direction or other vehicle while on ground or in-flight. For example, and without limitation, lift propulsor component 912 may include a rotor, propeller, paddle wheel and the like thereof, wherein a rotor is a component that produces torque along the longitudinal axis, and a propeller produces torquer along the vertical axis. In an embodiment, lift propulsor component 912 includes a plurality of blades. As used in this disclosure a “blade” is a propeller that converts rotary motion from an engine or other power source into a swirling slipstream. In an embodiment, blade may convert rotary motion to push the propeller forwards or backwards. In an embodiment lift propulsor component 912 may include a rotating power-driven hub, to which are attached several radial airfoil-section blades such that the whole assembly rotates about a longitudinal axis. Blades may be configured at an angle of attack, wherein an angle of attack is described in detail below. In an embodiment, and without limitation, angle of attack may include a fixed angle of attack. As used in this disclosure a “fixed angle of attack” is fixed angle between a chord line of a blade and relative wind. As used in this disclosure a “fixed angle” is an angle that is secured and/or unmovable from the attachment point. For example, and without limitation fixed angle of attack may be 3.2° as a function of a pitch angle of 19.7° and a relative wind angle 16.5°. In another embodiment, and without limitation, angle of attack may include a variable angle of attack. As used in this disclosure a “variable angle of attack” is a variable and/or moveable angle between a chord line of a blade and relative wind. As used in this disclosure a “variable angle” is an angle that is moveable from an attachment point. For example, and without limitation variable angle of attack may be a first angle of 9.7° as a function of a pitch angle of 17.1° and a relative wind angle 16.4°, wherein the angle adjusts and/or shifts to a second angle of 16.7° as a function of a pitch angle of 16.1° and a relative wind angle 16.4°. In an embodiment, angle of attack be configured to produce a fixed pitch angle. As used in this disclosure a “fixed pitch angle” is a fixed angle between a cord line of a blade and the rotational velocity direction. For example, and without limitation, fixed pitch angle may include 18°. In another embodiment fixed angle of attack may be manually variable to a few set positions to adjust one or more lifts of the aircraft prior to flight. In an embodiment, blades for an aircraft are designed to be fixed to their hub at an angle similar to the thread on a screw makes an angle to the shaft; this angle may be referred to as a pitch or pitch angle which will determine a speed of forward movement as the blade rotates.

In an embodiment, and still referring to FIG. 9 , lift propulsor component 912 may be configured to produce a lift. As used in this disclosure a “lift” is a perpendicular force to the oncoming flow direction of fluid surrounding the surface. For example, and without limitation relative air speed may be horizontal to aircraft 900, wherein lift force may be a force exerted in a vertical direction, directing aircraft 900 upwards. In an embodiment, and without limitation, lift propulsor component 912 may produce lift as a function of applying a torque to lift propulsor component. As used in this disclosure a “torque” is a measure of force that causes an object to rotate about an axis in a direction. For example, and without limitation, torque may rotate an aileron and/or rudder to generate a force that may adjust and/or affect altitude, airspeed velocity, groundspeed velocity, direction during flight, and/or thrust. For example, one or more flight components such as a power sources may apply a torque on lift propulsor component 912 to produce lift. As used in this disclosure a “power source” is a source that that drives and/or controls any other flight component. For example, and without limitation power source may include a motor that operates to move one or more lift propulsor components, to drive one or more blades, or the like thereof. A motor may be driven by direct current (DC) electric power and may include, without limitation, brushless DC electric motors, switched reluctance motors, induction motors, or any combination thereof. A motor may also include electronic speed controllers or other components for regulating motor speed, rotation direction, and/or dynamic braking.

Still referring to FIG. 9 , power source may include an energy source. An energy source may include, for example, an electrical energy source a generator, a photovoltaic device, a fuel cell such as a hydrogen fuel cell, direct methanol fuel cell, and/or solid oxide fuel cell, an electric energy storage device (e.g., a capacitor, an inductor, and/or a battery). An electrical energy source may also include a battery cell, or a plurality of battery cells connected in series into a module and each module connected in series or in parallel with other modules. Configuration of an energy source containing connected modules may be designed to meet an energy or power requirement and may be designed to fit within a designated footprint in an electric aircraft in which aircraft 900 may be incorporated.

In an embodiment, and still referring to FIG. 9 , an energy source may be used to provide a steady supply of electrical power to a load over the course of a flight by a vehicle or other electric aircraft. For example, an energy source may be capable of providing sufficient power for “cruising” and other relatively low-energy phases of flight. An energy source may also be capable of providing electrical power for some higher-power phases of flight as well, particularly when the energy source is at a high SOC, as may be the case for instance during takeoff. In an embodiment, an energy source may be capable of providing sufficient electrical power for auxiliary loads including without limitation, lighting, navigation, communications, de-icing, steering or other systems requiring power or energy. Further, an energy source may be capable of providing sufficient power for controlled descent and landing protocols, including, without limitation, hovering descent or runway landing. As used herein an energy source may have high power density where electrical power an energy source can usefully produce per unit of volume and/or mass is relatively high. “Electrical power,” as used in this disclosure, is defined as a rate of electrical energy per unit time. An energy source may include a device for which power that may be produced per unit of volume and/or mass has been optimized, at the expense of the maximal total specific energy density or power capacity, during design. Non-limiting examples of items that may be used as at least an energy source may include batteries used for starting applications including Li ion batteries which may include NCA, NMC, Lithium iron phosphate (LiFePO4) and Lithium Manganese Oxide (LMO) batteries, which may be mixed with another cathode chemistry to provide more specific power if the application requires Li metal batteries, which have a lithium metal anode that provides high power on demand, Li ion batteries that have a silicon or titanite anode, energy source may be used, in an embodiment, to provide electrical power to an electric aircraft or drone, such as an electric aircraft vehicle, during moments requiring high rates of power output, including without limitation takeoff, landing, thermal de-icing and situations requiring greater power output for reasons of stability, such as high turbulence situations, as described in further detail below. A battery may include, without limitation a battery using nickel based chemistries such as nickel cadmium or nickel metal hydride, a battery using lithium ion battery chemistries such as a nickel cobalt aluminum (NCA), nickel manganese cobalt (NMC), lithium iron phosphate (LiFePO4), lithium cobalt oxide (LCO), and/or lithium manganese oxide (LMO), a battery using lithium polymer technology, lead-based batteries such as without limitation lead acid batteries, metal-air batteries, or any other suitable battery. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of various devices of components that may be used as an energy source.

Still referring to FIG. 9 , an energy source may include a plurality of energy sources, referred to herein as a module of energy sources. A module may include batteries connected in parallel or in series or a plurality of modules connected either in series or in parallel designed to deliver both the power and energy requirements of the application. Connecting batteries in series may increase the voltage of at least an energy source which may provide more power on demand. High voltage batteries may require cell matching when high peak load is needed. As more cells are connected in strings, there may exist the possibility of one cell failing which may increase resistance in the module and reduce an overall power output as a voltage of the module may decrease as a result of that failing cell. Connecting batteries in parallel may increase total current capacity by decreasing total resistance, and it also may increase overall amp-hour capacity. Overall energy and power outputs of at least an energy source may be based on individual battery cell performance or an extrapolation based on measurement of at least an electrical parameter. In an embodiment where an energy source includes a plurality of battery cells, overall power output capacity may be dependent on electrical parameters of each individual cell. If one cell experiences high self-discharge during demand, power drawn from at least an energy source may be decreased to avoid damage to the weakest cell. An energy source may further include, without limitation, wiring, conduit, housing, cooling system and battery management system. Persons skilled in the art will be aware, after reviewing the entirety of this disclosure, of many different components of an energy source.

In an embodiment and still referring to FIG. 9 , plurality of flight components 908 may be arranged in a quad copter orientation. As used in this disclosure a “quad copter orientation” is at least a lift propulsor component oriented in a geometric shape and/or pattern, wherein each of the lift propulsor components are located along a vertex of the geometric shape. For example, and without limitation, a square quad copter orientation may have four lift propulsor components oriented in the geometric shape of a square, wherein each of the four lift propulsor components are located along the four vertices of the square shape. As a further non-limiting example, a hexagonal quad copter orientation may have six lift propulsor components oriented in the geometric shape of a hexagon, wherein each of the six lift propulsor components are located along the six vertices of the hexagon shape. In an embodiment, and without limitation, quad copter orientation may include a first set of lift propulsor components and a second set of lift propulsor components, wherein the first set of lift propulsor components and the second set of lift propulsor components may include two lift propulsor components each, wherein the first set of lift propulsor components and a second set of lift propulsor components are distinct from one another. For example, and without limitation, the first set of lift propulsor components may include two lift propulsor components that rotate in a clockwise direction, wherein the second set of lift propulsor components may include two lift propulsor components that rotate in a counterclockwise direction. In an embodiment, and without limitation, the first set of propulsor lift components may be oriented along a line oriented 95° from the longitudinal axis of aircraft 900. In another embodiment, and without limitation, the second set of propulsor lift components may be oriented along a line oriented 135° from the longitudinal axis, wherein the first set of lift propulsor components line and the second set of lift propulsor components are perpendicular to each other.

Still referring to FIG. 9 , plurality of flight components 908 may include a pusher component 916. As used in this disclosure a “pusher component” is a component that pushes and/or thrusts an aircraft through a medium. As a non-limiting example, pusher component 916 may include a pusher propeller, a paddle wheel, a pusher motor, a pusher propulsor, and the like. Additionally, or alternatively, pusher flight component may include a plurality of pusher flight components. Pusher component 916 is configured to produce a forward thrust. As used in this disclosure a “forward thrust” is a thrust that forces aircraft through a medium in a horizontal direction, wherein a horizontal direction is a direction parallel to the longitudinal axis. As a non-limiting example, forward thrust may include a force of 1145 N to force aircraft to in a horizontal direction along the longitudinal axis. As a further non-limiting example, forward thrust may include a force of, as a non-limiting example, 300 N to force aircraft 900 in a horizontal direction along a longitudinal axis. As a further non-limiting example, pusher component 916 may twist and/or rotate to pull air behind it and, at the same time, push aircraft 900 forward with an equal amount of force. In an embodiment, and without limitation, the more air forced behind aircraft, the greater the thrust force with which the aircraft is pushed horizontally will be. In another embodiment, and without limitation, forward thrust may force aircraft 900 through the medium of relative air. Additionally or alternatively, plurality of flight components 908 may include one or more puller components. As used in this disclosure a “puller component” is a component that pulls and/or tows an aircraft through a medium. As a non-limiting example, puller component may include a flight component such as a puller propeller, a puller motor, a tractor propeller, a puller propulsor, and the like. Additionally, or alternatively, puller component may include a plurality of puller flight components.

In an embodiment and still referring to FIG. 9 , aircraft 900 may include a flight controller located within fuselage 904, wherein a flight controller is described in detail below, in reference to FIG. 9 . In an embodiment, and without limitation, flight controller may be configured to operate a fixed-wing flight capability. As used in this disclosure a “fixed-wing flight capability” is a method of flight wherein the plurality of laterally extending elements generate lift. For example, and without limitation, fixed-wing flight capability may generate lift as a function of an airspeed of aircraft 100 and one or more airfoil shapes of the laterally extending elements, wherein an airfoil is described above in detail. As a further non-limiting example, flight controller may operate the fixed-wing flight capability as a function of reducing applied torque on lift propulsor component 912. For example, and without limitation, flight controller may reduce a torque of 19 Nm applied to a first set of lift propulsor components to a torque of 16 Nm. As a further non-limiting example, flight controller may reduce a torque of 12 Nm applied to a first set of lift propulsor components to a torque of 0 Nm. In an embodiment, and without limitation, flight controller may produce fixed-wing flight capability as a function of increasing forward thrust exerted by pusher component 916. For example, and without limitation, flight controller may increase a forward thrust of 900 kN produced by pusher component 916 to a forward thrust of 1669 kN. In an embodiment, and without limitation, an amount of lift generation may be related to an amount of forward thrust generated to increase airspeed velocity, wherein the amount of lift generation may be directly proportional to the amount of forward thrust produced. Additionally or alternatively, flight controller may include an inertia compensator. As used in this disclosure an “inertia compensator” is one or more computing devices, electrical components, logic circuits, processors, and the like there of that are configured to compensate for inertia in one or more lift propulsor components present in aircraft 900. Inertia compensator may alternatively or additionally include any computing device used as an inertia compensator as described in U.S. Nonprovisional application Ser. No. 17/106,557, and entitled “SYSTEM AND METHOD FOR FLIGHT CONTROL IN ELECTRIC AIRCRAFT,” the entirety of which is incorporated herein by reference.

In an embodiment, and still referring to FIG. 9 , flight controller may be configured to perform a reverse thrust command. As used in this disclosure a “reverse thrust command” is a command to perform a thrust that forces a medium towards the relative air opposing aircraft 190. For example, reverse thrust command may include a thrust of 180 N directed towards the nose of aircraft to at least repel and/or oppose the relative air. Reverse thrust command may alternatively or additionally include any reverse thrust command as described in U.S. Nonprovisional application Ser. No. 17/319,155 and entitled “AIRCRAFT HAVING REVERSE THRUST CAPABILITIES,” the entirety of which is incorporated herein by reference. In another embodiment, flight controller may be configured to perform a regenerative drag operation. As used in this disclosure a “regenerative drag operation” is an operating condition of an aircraft, wherein the aircraft has a negative thrust and/or is reducing in airspeed velocity. For example, and without limitation, regenerative drag operation may include a positive propeller speed and a negative propeller thrust. Regenerative drag operation may alternatively or additionally include any regenerative drag operation as described in U.S. Nonprovisional application Ser. No. 17/319,155.

In an embodiment, and still referring to FIG. 9 , flight controller may be configured to perform a corrective action as a function of a failure event. As used in this disclosure a “corrective action” is an action conducted by the plurality of flight components to correct and/or alter a movement of an aircraft. For example, and without limitation, a corrective action may include an action to reduce a yaw torque generated by a failure event. Additionally or alternatively, corrective action may include any corrective action as described in U.S. Nonprovisional application Ser. No. 17/222,539, and entitled “AIRCRAFT FOR SELF-NEUTRALIZING FLIGHT,” the entirety of which is incorporated herein by reference. As used in this disclosure a “failure event” is a failure of a lift propulsor component of the plurality of lift propulsor components. For example, and without limitation, a failure event may denote a rotation degradation of a rotor, a reduced torque of a rotor, and the like thereof.

Now referring to FIG. 10 , an exemplary embodiment 1000 of a flight controller 1004 is illustrated. As used in this disclosure a “flight controller” is a computing device of a plurality of computing devices dedicated to data storage, security, distribution of traffic for load balancing, and flight instruction. Flight controller 1004 may include and/or communicate with any computing device as described in this disclosure, including without limitation a microcontroller, microprocessor, digital signal processor (DSP) and/or system on a chip (SoC) as described in this disclosure. Further, flight controller 1004 may include a single computing device operating independently, or may include two or more computing device operating in concert, in parallel, sequentially or the like; two or more computing devices may be included together in a single computing device or in two or more computing devices. In embodiments, flight controller 1004 may be installed in an aircraft, may control the aircraft remotely, and/or may include an element installed in the aircraft and a remote element in communication therewith. In some embodiments, flight controller 1004 may be configured to generate a node as described in FIG. 2 .

In an embodiment, and still referring to FIG. 10 , flight controller 1004 may include a signal transformation component 1008. As used in this disclosure a “signal transformation component” is a component that transforms and/or converts a first signal to a second signal, wherein a signal may include one or more digital and/or analog signals. For example, and without limitation, signal transformation component 1008 may be configured to perform one or more operations such as preprocessing, lexical analysis, parsing, semantic analysis, and the like thereof. In an embodiment, and without limitation, signal transformation component 1008 may include one or more analog-to-digital convertors that transform a first signal of an analog signal to a second signal of a digital signal. For example, and without limitation, an analog-to-digital converter may convert an analog input signal to a 10-bit binary digital representation of that signal. In another embodiment, signal transformation component 1008 may include transforming one or more low-level languages such as, but not limited to, machine languages and/or assembly languages. For example, and without limitation, signal transformation component 1008 may include transforming a binary language signal to an assembly language signal. In an embodiment, and without limitation, signal transformation component 1008 may include transforming one or more high-level languages and/or formal languages such as but not limited to alphabets, strings, and/or languages. For example, and without limitation, high-level languages may include one or more system languages, scripting languages, domain-specific languages, visual languages, esoteric languages, and the like thereof. As a further non-limiting example, high-level languages may include one or more algebraic formula languages, business data languages, string and list languages, object-oriented languages, and the like thereof.

Still referring to FIG. 10 , signal transformation component 1008 may be configured to optimize an intermediate representation 1012. As used in this disclosure an “intermediate representation” is a data structure and/or code that represents the input signal. Signal transformation component 1008 may optimize intermediate representation as a function of a data-flow analysis, dependence analysis, alias analysis, pointer analysis, escape analysis, and the like thereof. In an embodiment, and without limitation, signal transformation component 1008 may optimize intermediate representation 1012 as a function of one or more inline expansions, dead code eliminations, constant propagation, loop transformations, and/or automatic parallelization functions. In another embodiment, signal transformation component 1008 may optimize intermediate representation as a function of a machine dependent optimization such as a peephole optimization, wherein a peephole optimization may rewrite short sequences of code into more efficient sequences of code. Signal transformation component 1008 may optimize intermediate representation to generate an output language, wherein an “output language,” as used herein, is the native machine language of flight controller 1004. For example, and without limitation, native machine language may include one or more binary and/or numerical languages.

In an embodiment, and without limitation, signal transformation component 1008 may include transform one or more inputs and outputs as a function of an error correction code. An error correction code, also known as error correcting code (ECC), is an encoding of a message or lot of data using redundant information, permitting recovery of corrupted data. An ECC may include a block code, in which information is encoded on fixed-size packets and/or blocks of data elements such as symbols of predetermined size, bits, or the like. Reed-Solomon coding, in which message symbols within a symbol set having q symbols are encoded as coefficients of a polynomial of degree less than or equal to a natural number k, over a finite field F with q elements; strings so encoded have a minimum hamming distance of k+1, and permit correction of (q−k−1)/2 erroneous symbols. Block code may alternatively or additionally be implemented using Golay coding, also known as binary Golay coding, Bose-Chaudhuri, Hocquenghuem (BCH) coding, multidimensional parity-check coding, and/or Hamming codes. An ECC may alternatively or additionally be based on a convolutional code.

In an embodiment, and still referring to FIG. 10 , flight controller 1004 may include a reconfigurable hardware platform 1016. A “reconfigurable hardware platform,” as used herein, is a component and/or unit of hardware that may be reprogrammed, such that, for instance, a data path between elements such as logic gates or other digital circuit elements may be modified to change an algorithm, state, logical sequence, or the like of the component and/or unit. This may be accomplished with such flexible high-speed computing fabrics as field-programmable gate arrays (FPGAs), which may include a grid of interconnected logic gates, connections between which may be severed and/or restored to program in modified logic. Reconfigurable hardware platform 1016 may be reconfigured to enact any algorithm and/or algorithm selection process received from another computing device and/or created using machine-learning processes.

Still referring to FIG. 10 , reconfigurable hardware platform 1016 may include a logic component 1020. As used in this disclosure a “logic component” is a component that executes instructions on output language. For example, and without limitation, logic component may perform basic arithmetic, logic, controlling, input/output operations, and the like thereof. Logic component 1020 may include any suitable processor, such as without limitation a component incorporating logical circuitry for performing arithmetic and logical operations, such as an arithmetic and logic unit (ALU), which may be regulated with a state machine and directed by operational inputs from memory and/or sensors; logic component 1020 may be organized according to Von Neumann and/or Harvard architecture as a non-limiting example. Logic component 1020 may include, incorporate, and/or be incorporated in, without limitation, a microcontroller, microprocessor, digital signal processor (DSP), Field Programmable Gate Array (FPGA), Complex Programmable Logic Device (CPLD), Graphical Processing Unit (GPU), general purpose GPU, Tensor Processing Unit (TPU), analog or mixed signal processor, Trusted Platform Module (TPM), a floating-point unit (FPU), and/or system on a chip (SoC). In an embodiment, logic component 1020 may include one or more integrated circuit microprocessors, which may contain one or more central processing units, central processors, and/or main processors, on a single metal-oxide-semiconductor chip. Logic component 1020 may be configured to execute a sequence of stored instructions to be performed on the output language and/or intermediate representation 1012. Logic component 1020 may be configured to fetch and/or retrieve the instruction from a memory cache, wherein a “memory cache,” as used in this disclosure, is a stored instruction set on flight controller 1004. Logic component 1020 may be configured to decode the instruction retrieved from the memory cache to opcodes and/or operands. Logic component 1020 may be configured to execute the instruction on intermediate representation 1012 and/or output language. For example, and without limitation, logic component 1020 may be configured to execute an addition operation on intermediate representation 1012 and/or output language.

In an embodiment, and without limitation, logic component 1020 may be configured to calculate a flight element 1024. As used in this disclosure a “flight element” is an element of datum denoting a relative status of aircraft. For example, and without limitation, flight element 1024 may denote one or more torques, thrusts, airspeed velocities, forces, altitudes, groundspeed velocities, directions during flight, directions facing, forces, orientations, and the like thereof. For example, and without limitation, flight element 1024 may denote that aircraft is cruising at an altitude and/or with a sufficient magnitude of forward thrust. As a further non-limiting example, flight status may denote that is building thrust and/or groundspeed velocity in preparation for a takeoff. As a further non-limiting example, flight element 1024 may denote that aircraft is following a flight path accurately and/or sufficiently.

Still referring to FIG. 10 , flight controller 1004 may include a chipset component 1028. As used in this disclosure a “chipset component” is a component that manages data flow. In an embodiment, and without limitation, chipset component 1028 may include a northbridge data flow path, wherein the northbridge dataflow path may manage data flow from logic component 1020 to a high-speed device and/or component, such as a RAM, graphics controller, and the like thereof. In another embodiment, and without limitation, chipset component 1028 may include a southbridge data flow path, wherein the southbridge dataflow path may manage data flow from logic component 1020 to lower-speed peripheral buses, such as a peripheral component interconnect (PCI), industry standard architecture (ICA), and the like thereof. In an embodiment, and without limitation, southbridge data flow path may include managing data flow between peripheral connections such as ethernet, USB, audio devices, and the like thereof. Additionally or alternatively, chipset component 1028 may manage data flow between logic component 1020, memory cache, and a flight component 1032. As used in this disclosure a “flight component” is a portion of an aircraft that can be moved or adjusted to affect one or more flight elements. For example, flight component 1032 may include a component used to affect the aircrafts' roll and pitch which may comprise one or more ailerons. As a further example, flight component 1032 may include a rudder to control yaw of an aircraft. In an embodiment, chipset component 1028 may be configured to communicate with a plurality of flight components as a function of flight element 1024. For example, and without limitation, chipset component 1028 may transmit to an aircraft rotor to reduce torque of a first lift propulsor and increase the forward thrust produced by a pusher component to perform a flight maneuver.

In an embodiment, and still referring to FIG. 10 , flight controller 1004 may be configured generate an autonomous function. As used in this disclosure an “autonomous function” is a mode and/or function of flight controller 1004 that controls aircraft automatically. For example, and without limitation, autonomous function may perform one or more aircraft maneuvers, take offs, landings, altitude adjustments, flight leveling adjustments, turns, climbs, and/or descents. As a further non-limiting example, autonomous function may adjust one or more airspeed velocities, thrusts, torques, and/or groundspeed velocities. As a further non-limiting example, autonomous function may perform one or more flight path corrections and/or flight path modifications as a function of flight element 1024. In an embodiment, autonomous function may include one or more modes of autonomy such as, but not limited to, autonomous mode, semi-autonomous mode, and/or non-autonomous mode. As used in this disclosure “autonomous mode” is a mode that automatically adjusts and/or controls aircraft and/or the maneuvers of aircraft in its entirety. For example, autonomous mode may denote that flight controller 1004 will adjust the aircraft. As used in this disclosure a “semi-autonomous mode” is a mode that automatically adjusts and/or controls a portion and/or section of aircraft. For example, and without limitation, semi-autonomous mode may denote that a pilot will control the propulsors, wherein flight controller 1004 will control the ailerons and/or rudders. As used in this disclosure “non-autonomous mode” is a mode that denotes a pilot will control aircraft and/or maneuvers of aircraft in its entirety.

In an embodiment, and still referring to FIG. 10 , flight controller 1004 may generate autonomous function as a function of an autonomous machine-learning model. As used in this disclosure an “autonomous machine-learning model” is a machine-learning model to produce an autonomous function output given flight element 1024 and a pilot signal 1036 as inputs; this is in contrast to a non-machine learning software program where the commands to be executed are determined in advance by a user and written in a programming language. As used in this disclosure a “pilot signal” is an element of datum representing one or more functions a pilot is controlling and/or adjusting. For example, pilot signal 1036 may denote that a pilot is controlling and/or maneuvering ailerons, wherein the pilot is not in control of the rudders and/or propulsors. In an embodiment, pilot signal 1036 may include an implicit signal and/or an explicit signal. For example, and without limitation, pilot signal 1036 may include an explicit signal, wherein the pilot explicitly states there is a lack of control and/or desire for autonomous function. As a further non-limiting example, pilot signal 1036 may include an explicit signal directing flight controller 1004 to control and/or maintain a portion of aircraft, a portion of the flight plan, the entire aircraft, and/or the entire flight plan. As a further non-limiting example, pilot signal 1036 may include an implicit signal, wherein flight controller 1004 detects a lack of control such as by a malfunction, torque alteration, flight path deviation, and the like thereof. In an embodiment, and without limitation, pilot signal 1036 may include one or more explicit signals to reduce torque, and/or one or more implicit signals that torque may be reduced due to reduction of airspeed velocity. In an embodiment, and without limitation, pilot signal 1036 may include one or more local and/or global signals. For example, and without limitation, pilot signal 1036 may include a local signal that is transmitted by a pilot and/or crew member. As a further non-limiting example, pilot signal 1036 may include a global signal that is transmitted by air traffic control and/or one or more remote users that are in communication with the pilot of aircraft. In an embodiment, pilot signal 1036 may be received as a function of a tri-state bus and/or multiplexor that denotes an explicit pilot signal should be transmitted prior to any implicit or global pilot signal.

Still referring to FIG. 10 , autonomous machine-learning model may include one or more autonomous machine-learning processes such as supervised, unsupervised, or reinforcement machine-learning processes that flight controller 1004 and/or a remote device may or may not use in the generation of autonomous function. As used in this disclosure “remote device” is an external device to flight controller 1004. Additionally or alternatively, autonomous machine-learning model may include one or more autonomous machine-learning processes that a field-programmable gate array (FPGA) may or may not use in the generation of autonomous function. Autonomous machine-learning process may include, without limitation machine learning processes such as simple linear regression, multiple linear regression, polynomial regression, support vector regression, ridge regression, lasso regression, elasticnet regression, decision tree regression, random forest regression, logistic regression, logistic classification, K-nearest neighbors, support vector machines, kernel support vector machines, naïve bayes, decision tree classification, random forest classification, K-means clustering, hierarchical clustering, dimensionality reduction, principal component analysis, linear discriminant analysis, kernel principal component analysis, Q-learning, State Action Reward State Action (SARSA), Deep-Q network, Markov decision processes, Deep Deterministic Policy Gradient (DDPG), or the like thereof.

In an embodiment, and still referring to FIG. 10 , autonomous machine learning model may be trained as a function of autonomous training data, wherein autonomous training data may correlate a flight element, pilot signal, and/or simulation data to an autonomous function. For example, and without limitation, a flight element of an airspeed velocity, a pilot signal of limited and/or no control of propulsors, and a simulation data of required airspeed velocity to reach the destination may result in an autonomous function that includes a semi-autonomous mode to increase thrust of the propulsors. Autonomous training data may be received as a function of user-entered valuations of flight elements, pilot signals, simulation data, and/or autonomous functions. Flight controller 1004 may receive autonomous training data by receiving correlations of flight element, pilot signal, and/or simulation data to an autonomous function that were previously received and/or determined during a previous iteration of generation of autonomous function. Autonomous training data may be received by one or more remote devices and/or FPGAs that at least correlate a flight element, pilot signal, and/or simulation data to an autonomous function. Autonomous training data may be received in the form of one or more user-entered correlations of a flight element, pilot signal, and/or simulation data to an autonomous function.

Still referring to FIG. 10 , flight controller 1004 may receive autonomous machine-learning model from a remote device and/or FPGA that utilizes one or more autonomous machine learning processes, wherein a remote device and an FPGA is described above in detail. For example, and without limitation, a remote device may include a computing device, external device, processor, FPGA, microprocessor and the like thereof. Remote device and/or FPGA may perform the autonomous machine-learning process using autonomous training data to generate autonomous function and transmit the output to flight controller 1004. Remote device and/or FPGA may transmit a signal, bit, datum, or parameter to flight controller 1004 that at least relates to autonomous function. Additionally or alternatively, the remote device and/or FPGA may provide an updated machine-learning model. For example, and without limitation, an updated machine-learning model may be comprised of a firmware update, a software update, an autonomous machine-learning process correction, and the like thereof. As a non-limiting example a software update may incorporate a new simulation data that relates to a modified flight element. Additionally or alternatively, the updated machine learning model may be transmitted to the remote device and/or FPGA, wherein the remote device and/or FPGA may replace the autonomous machine-learning model with the updated machine-learning model and generate the autonomous function as a function of the flight element, pilot signal, and/or simulation data using the updated machine-learning model. The updated machine-learning model may be transmitted by the remote device and/or FPGA and received by flight controller 1004 as a software update, firmware update, or corrected autonomous machine-learning model. For example, and without limitation autonomous machine learning model may utilize a neural net machine-learning process, wherein the updated machine-learning model may incorporate a gradient boosting machine-learning process.

Still referring to FIG. 10 , flight controller 1004 may include, be included in, and/or communicate with a mobile device such as a mobile telephone or smartphone. Further, flight controller may communicate with one or more additional devices as described below in further detail via a network interface device. The network interface device may be utilized for commutatively connecting a flight controller to one or more of a variety of networks, and one or more devices. Examples of a network interface device include, but are not limited to, a network interface card (e.g., a mobile network interface card, a LAN card), a modem, and any combination thereof. Examples of a network include, but are not limited to, a wide area network (e.g., the Internet, an enterprise network), a local area network (e.g., a network associated with an office, a building, a campus or other relatively small geographic space), a telephone network, a data network associated with a telephone/voice provider (e.g., a mobile communications provider data and/or voice network), a direct connection between two computing devices, and any combinations thereof. The network may include any network topology and can may employ a wired and/or a wireless mode of communication.

In an embodiment, and still referring to FIG. 10 , flight controller 1004 may include, but is not limited to, for example, a cluster of flight controllers in a first location and a second flight controller or cluster of flight controllers in a second location. Flight controller 1004 may include one or more flight controllers dedicated to data storage, security, distribution of traffic for load balancing, and the like. Flight controller 1004 may be configured to distribute one or more computing tasks as described below across a plurality of flight controllers, which may operate in parallel, in series, redundantly, or in any other manner used for distribution of tasks or memory between computing devices. For example, and without limitation, flight controller 1004 may implement a control algorithm to distribute and/or command the plurality of flight controllers. As used in this disclosure a “control algorithm” is a finite sequence of well-defined computer implementable instructions that may determine the flight component of the plurality of flight components to be adjusted. For example, and without limitation, control algorithm may include one or more algorithms that reduce and/or prevent aviation asymmetry. As a further non-limiting example, control algorithms may include one or more models generated as a function of a software including, but not limited to Simulink by MathWorks, Natick, Mass., USA. In an embodiment, and without limitation, control algorithm may be configured to generate an auto-code, wherein an “auto-code,” is used herein, is a code and/or algorithm that is generated as a function of the one or more models and/or software's. In another embodiment, control algorithm may be configured to produce a segmented control algorithm. As used in this disclosure a “segmented control algorithm” is control algorithm that has been separated and/or parsed into discrete sections. For example, and without limitation, segmented control algorithm may parse control algorithm into two or more segments, wherein each segment of control algorithm may be performed by one or more flight controllers operating on distinct flight components.

In an embodiment, and still referring to FIG. 10 , control algorithm may be configured to determine a segmentation boundary as a function of segmented control algorithm. As used in this disclosure a “segmentation boundary” is a limit and/or delineation associated with the segments of the segmented control algorithm. For example, and without limitation, segmentation boundary may denote that a segment in the control algorithm has a first starting section and/or a first ending section. As a further non-limiting example, segmentation boundary may include one or more boundaries associated with an ability of flight component 1032. In an embodiment, control algorithm may be configured to create an optimized signal communication as a function of segmentation boundary. For example, and without limitation, optimized signal communication may include identifying the discrete timing required to transmit and/or receive the one or more segmentation boundaries. In an embodiment, and without limitation, creating optimized signal communication further comprises separating a plurality of signal codes across the plurality of flight controllers. For example, and without limitation the plurality of flight controllers may include one or more formal networks, wherein formal networks transmit data along an authority chain and/or are limited to task-related communications. As a further non-limiting example, communication network may include informal networks, wherein informal networks transmit data in any direction. In an embodiment, and without limitation, the plurality of flight controllers may include a chain path, wherein a “chain path,” as used herein, is a linear communication path comprising a hierarchy that data may flow through. In an embodiment, and without limitation, the plurality of flight controllers may include an all-channel path, wherein an “all-channel path,” as used herein, is a communication path that is not restricted to a particular direction. For example, and without limitation, data may be transmitted upward, downward, laterally, and the like thereof. In an embodiment, and without limitation, the plurality of flight controllers may include one or more neural networks that assign a weighted value to a transmitted datum. For example, and without limitation, a weighted value may be assigned as a function of one or more signals denoting that a flight component is malfunctioning and/or in a failure state.

Still referring to FIG. 10 , the plurality of flight controllers may include a master bus controller. As used in this disclosure a “master bus controller” is one or more devices and/or components that are connected to a bus to initiate a direct memory access transaction, wherein a bus is one or more terminals in a bus architecture. Master bus controller may communicate using synchronous and/or asynchronous bus control protocols. In an embodiment, master bus controller may include flight controller 1004. In another embodiment, master bus controller may include one or more universal asynchronous receiver-transmitters (UART). For example, and without limitation, master bus controller may include one or more bus architectures that allow a bus to initiate a direct memory access transaction from one or more buses in the bus architectures. As a further non-limiting example, master bus controller may include one or more peripheral devices and/or components to communicate with another peripheral device and/or component and/or the master bus controller. In an embodiment, master bus controller may be configured to perform bus arbitration. As used in this disclosure “bus arbitration” is method and/or scheme to prevent multiple buses from attempting to communicate with and/or connect to master bus controller. For example and without limitation, bus arbitration may include one or more schemes such as a small computer interface system, wherein a small computer interface system is a set of standards for physical connecting and transferring data between peripheral devices and master bus controller by defining commands, protocols, electrical, optical, and/or logical interfaces. In an embodiment, master bus controller may receive intermediate representation 1012 and/or output language from logic component 1020, wherein output language may include one or more analog-to-digital conversions, low bit rate transmissions, message encryptions, digital signals, binary signals, logic signals, analog signals, and the like thereof described above in detail.

Still referring to FIG. 10 , master bus controller may communicate with a slave bus. As used in this disclosure a “slave bus” is one or more peripheral devices and/or components that initiate a bus transfer. For example, and without limitation, slave bus may receive one or more controls and/or asymmetric communications from master bus controller, wherein slave bus transfers data stored to master bus controller. In an embodiment, and without limitation, slave bus may include one or more internal buses, such as but not limited to a/an internal data bus, memory bus, system bus, front-side bus, and the like thereof. In another embodiment, and without limitation, slave bus may include one or more external buses such as external flight controllers, external computers, remote devices, printers, aircraft computer systems, flight control systems, and the like thereof.

In an embodiment, and still referring to FIG. 10 , control algorithm may optimize signal communication as a function of determining one or more discrete timings. For example, and without limitation master bus controller may synchronize timing of the segmented control algorithm by injecting high priority timing signals on a bus of the master bus control. As used in this disclosure a “high priority timing signal” is information denoting that the information is important. For example, and without limitation, high priority timing signal may denote that a section of control algorithm is of high priority and should be analyzed and/or transmitted prior to any other sections being analyzed and/or transmitted. In an embodiment, high priority timing signal may include one or more priority packets. As used in this disclosure a “priority packet” is a formatted unit of data that is communicated between the plurality of flight controllers. For example, and without limitation, priority packet may denote that a section of control algorithm should be used and/or is of greater priority than other sections.

Still referring to FIG. 10 , flight controller 1004 may also be implemented using a “shared nothing” architecture in which data is cached at the worker, in an embodiment, this may enable scalability of aircraft and/or computing device. Flight controller 1004 may include a distributer flight controller. As used in this disclosure a “distributer flight controller” is a component that adjusts and/or controls a plurality of flight components as a function of a plurality of flight controllers. For example, distributer flight controller may include a flight controller that communicates with a plurality of additional flight controllers and/or clusters of flight controllers. In an embodiment, distributed flight control may include one or more neural networks. For example, neural network also known as an artificial neural network, is a network of “nodes,” or data structures having one or more inputs, one or more outputs, and a function determining outputs based on inputs. Such nodes may be organized in a network, such as without limitation a convolutional neural network, including an input layer of nodes, one or more intermediate layers, and an output layer of nodes. Connections between nodes may be created via the process of “training” the network, in which elements from a training dataset are applied to the input nodes, a suitable training algorithm (such as Levenberg-Marquardt, conjugate gradient, simulated annealing, or other algorithms) is then used to adjust the connections and weights between nodes in adjacent layers of the neural network to produce the desired values at the output nodes. This process is sometimes referred to as deep learning.

Still referring to FIG. 10 , a node may include, without limitation a plurality of inputs x_(i) that may receive numerical values from inputs to a neural network containing the node and/or from other nodes. Node may perform a weighted sum of inputs using weights w_(i) that are multiplied by respective inputs x_(i). Additionally or alternatively, a bias b may be added to the weighted sum of the inputs such that an offset is added to each unit in the neural network layer that is independent of the input to the layer. The weighted sum may then be input into a function φ, which may generate one or more outputs y. Weight w_(i) applied to an input x_(i) may indicate whether the input is “excitatory,” indicating that it has strong influence on the one or more outputs y, for instance by the corresponding weight having a large numerical value, and/or a “inhibitory,” indicating it has a weak effect influence on the one more inputs y, for instance by the corresponding weight having a small numerical value. The values of weights w_(i) may be determined by training a neural network using training data, which may be performed using any suitable process as described above. In an embodiment, and without limitation, a neural network may receive semantic units as inputs and output vectors representing such semantic units according to weights w_(i) that are derived using machine-learning processes as described in this disclosure.

Still referring to FIG. 10 , flight controller may include a sub-controller 1040. As used in this disclosure a “sub-controller” is a controller and/or component that is part of a distributed controller as described above; for instance, flight controller 1004 may be and/or include a distributed flight controller made up of one or more sub-controllers. For example, and without limitation, sub-controller 1040 may include any controllers and/or components thereof that are similar to distributed flight controller and/or flight controller as described above. Sub-controller 1040 may include any component of any flight controller as described above. Sub-controller 1040 may be implemented in any manner suitable for implementation of a flight controller as described above. As a further non-limiting example, sub-controller 1040 may include one or more processors, logic components and/or computing devices capable of receiving, processing, and/or transmitting data across the distributed flight controller as described above. As a further non-limiting example, sub-controller 1040 may include a controller that receives a signal from a first flight controller and/or first distributed flight controller component and transmits the signal to a plurality of additional sub-controllers and/or flight components.

Still referring to FIG. 10 , flight controller may include a co-controller 1044. As used in this disclosure a “co-controller” is a controller and/or component that joins flight controller 1004 as components and/or nodes of a distributer flight controller as described above. For example, and without limitation, co-controller 1044 may include one or more controllers and/or components that are similar to flight controller 1004. As a further non-limiting example, co-controller 1044 may include any controller and/or component that joins flight controller 1004 to distributer flight controller. As a further non-limiting example, co-controller 1044 may include one or more processors, logic components and/or computing devices capable of receiving, processing, and/or transmitting data to and/or from flight controller 1004 to distributed flight control system. Co-controller 1044 may include any component of any flight controller as described above. Co-controller 1044 may be implemented in any manner suitable for implementation of a flight controller as described above.

In an embodiment, and with continued reference to FIG. 10 , flight controller 1004 may be designed and/or configured to perform any method, method step, or sequence of method steps in any embodiment described in this disclosure, in any order and with any degree of repetition. For instance, flight controller 1004 may be configured to perform a single step or sequence repeatedly until a desired or commanded outcome is achieved; repetition of a step or a sequence of steps may be performed iteratively and/or recursively using outputs of previous repetitions as inputs to subsequent repetitions, aggregating inputs and/or outputs of repetitions to produce an aggregate result, reduction or decrement of one or more variables such as global variables, and/or division of a larger processing task into a set of iteratively addressed smaller processing tasks. Flight controller may perform any step or sequence of steps as described in this disclosure in parallel, such as simultaneously and/or substantially simultaneously performing a step two or more times using two or more parallel threads, processor cores, or the like; division of tasks between parallel threads and/or processes may be performed according to any protocol suitable for division of tasks between iterations. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of various ways in which steps, sequences of steps, processing tasks, and/or data may be subdivided, shared, or otherwise dealt with using iteration, recursion, and/or parallel processing

Referring now to FIG. 11 , an exemplary embodiment of a machine-learning module 1100 that may perform one or more machine-learning processes as described in this disclosure is illustrated. Machine-learning module may perform determinations, classification, and/or analysis steps, methods, processes, or the like as described in this disclosure using machine learning processes. A “machine learning process,” as used in this disclosure, is a process that automatedly uses training data 1104 to generate an algorithm that will be performed by a computing device/module to produce outputs 1108 given data provided as inputs 1112; this is in contrast to a non-machine learning software program where the commands to be executed are determined in advance by a user and written in a programming language.

Still referring to FIG. 11 , “training data,” as used herein, is data containing correlations that a machine-learning process may use to model relationships between two or more categories of data elements. For instance, and without limitation, training data 1104 may include a plurality of data entries, each entry representing a set of data elements that were recorded, received, and/or generated together; data elements may be correlated by shared existence in a given data entry, by proximity in a given data entry, or the like. Multiple data entries in training data 1104 may evince one or more trends in correlations between categories of data elements; for instance, and without limitation, a higher value of a first data element belonging to a first category of data element may tend to correlate to a higher value of a second data element belonging to a second category of data element, indicating a possible proportional or other mathematical relationship linking values belonging to the two categories. Multiple categories of data elements may be related in training data 1104 according to various correlations; correlations may indicate causative and/or predictive links between categories of data elements, which may be modeled as relationships such as mathematical relationships by machine-learning processes as described in further detail below. Training data 1104 may be formatted and/or organized by categories of data elements, for instance by associating data elements with one or more descriptors corresponding to categories of data elements. As a non-limiting example, training data 1104 may include data entered in standardized forms by persons or processes, such that entry of a given data element in a given field in a form may be mapped to one or more descriptors of categories. Elements in training data 1104 may be linked to descriptors of categories by tags, tokens, or other data elements; for instance, and without limitation, training data 1104 may be provided in fixed-length formats, formats linking positions of data to categories such as comma-separated value (CSV) formats and/or self-describing formats such as extensible markup language (XML), JavaScript Object Notation (JSON), or the like, enabling processes or devices to detect categories of data.

Alternatively or additionally, and continuing to refer to FIG. 11 , training data 1104 may include one or more elements that are not categorized; that is, training data 1104 may not be formatted or contain descriptors for some elements of data. Machine-learning algorithms and/or other processes may sort training data 1104 according to one or more categorizations using, for instance, natural language processing algorithms, tokenization, detection of correlated values in raw data and the like; categories may be generated using correlation and/or other processing algorithms. As a non-limiting example, in a corpus of text, phrases making up a number “n” of compound words, such as nouns modified by other nouns, may be identified according to a statistically significant prevalence of n-grams containing such words in a particular order; such an n-gram may be categorized as an element of language such as a “word” to be tracked similarly to single words, generating a new category as a result of statistical analysis. Similarly, in a data entry including some textual data, a person's name may be identified by reference to a list, dictionary, or other compendium of terms, permitting ad-hoc categorization by machine-learning algorithms, and/or automated association of data in the data entry with descriptors or into a given format. The ability to categorize data entries automatedly may enable the same training data 1104 to be made applicable for two or more distinct machine-learning algorithms as described in further detail below. Training data 1104 used by machine-learning module 1100 may correlate any input data as described in this disclosure to any output data as described in this disclosure. As a non-limiting illustrative example a vehicle data may be an input and an output may include a vehicle model output. As a non-limiting illustrative example, vehicle data and vehicle model output may be inputs and a vehicle collection datum may be an output.

Further referring to FIG. 11 , training data may be filtered, sorted, and/or selected using one or more supervised and/or unsupervised machine-learning processes and/or models as described in further detail below; such models may include without limitation a training data classifier 1116. Training data classifier 1116 may include a “classifier,” which as used in this disclosure is a machine-learning model as defined below, such as a mathematical model, neural net, or program generated by a machine learning algorithm known as a “classification algorithm,” as described in further detail below, that sorts inputs into categories or bins of data, outputting the categories or bins of data and/or labels associated therewith. A classifier may be configured to output at least a datum that labels or otherwise identifies a set of data that are clustered together, found to be close under a distance metric as described below, or the like. Machine-learning module 1100 may generate a classifier using a classification algorithm, defined as a processes whereby a computing device and/or any module and/or component operating thereon derives a classifier from training data 1104. Classification may be performed using, without limitation, linear classifiers such as without limitation logistic regression and/or naive Bayes classifiers, nearest neighbor classifiers such as k-nearest neighbors classifiers, support vector machines, least squares support vector machines, fisher's linear discriminant, quadratic classifiers, decision trees, boosted trees, random forest classifiers, learning vector quantization, and/or neural network-based classifiers. As a non-limiting example, training data classifier 1116 may classify elements of training data to various stages of flight denoted by a timer module for which a subset of training data may be selected.

Still referring to FIG. 11 , machine-learning module 1100 may be configured to perform a lazy-learning process 1120 and/or protocol, which may alternatively be referred to as a “lazy loading” or “call-when-needed” process and/or protocol, may be a process whereby machine learning is conducted upon receipt of an input to be converted to an output, by combining the input and training set to derive the algorithm to be used to produce the output on demand. For instance, an initial set of simulations may be performed to cover an initial heuristic and/or “first guess” at an output and/or relationship. As a non-limiting example, an initial heuristic may include a ranking of associations between inputs and elements of training data 1104. Heuristic may include selecting some number of highest-ranking associations and/or training data 1104 elements. Lazy learning may implement any suitable lazy learning algorithm, including without limitation a K-nearest neighbors algorithm, a lazy naïve Bayes algorithm, or the like; persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of various lazy-learning algorithms that may be applied to generate outputs as described in this disclosure, including without limitation lazy learning applications of machine-learning algorithms as described in further detail below.

Alternatively or additionally, and with continued reference to FIG. 11 , machine-learning processes as described in this disclosure may be used to generate machine-learning models 1124. A “machine-learning model,” as used in this disclosure, is a mathematical and/or algorithmic representation of a relationship between inputs and outputs, as generated using any machine-learning process including without limitation any process as described above, and stored in memory; an input is submitted to a machine-learning model 1124 once created, which generates an output based on the relationship that was derived. For instance, and without limitation, a linear regression model, generated using a linear regression algorithm, may compute a linear combination of input data using coefficients derived during machine-learning processes to calculate an output datum. As a further non-limiting example, a machine-learning model 1124 may be generated by creating an artificial neural network, such as a convolutional neural network comprising an input layer of nodes, one or more intermediate layers, and an output layer of nodes. Connections between nodes may be created via the process of “training” the network, in which elements from a training data 1104 set are applied to the input nodes, a suitable training algorithm (such as Levenberg-Marquardt, conjugate gradient, simulated annealing, or other algorithms) is then used to adjust the connections and weights between nodes in adjacent layers of the neural network to produce the desired values at the output nodes. This process is sometimes referred to as deep learning.

Still referring to FIG. 11 , machine-learning algorithms may include at least a supervised machine-learning process 1128. At least a supervised machine-learning process 1128, as defined herein, include algorithms that receive a training set relating a number of inputs to a number of outputs, and seek to find one or more mathematical relations relating inputs to outputs, where each of the one or more mathematical relations is optimal according to some criterion specified to the algorithm using some scoring function. For instance, a supervised learning algorithm may include any inputs as described herein as inputs, [any outputs described herein as outputs, and a scoring function representing a desired form of relationship to be detected between inputs and outputs; scoring function may, for instance, seek to maximize the probability that a given input and/or combination of elements inputs is associated with a given output to minimize the probability that a given input is not associated with a given output. Scoring function may be expressed as a risk function representing an “expected loss” of an algorithm relating inputs to outputs, where loss is computed as an error function representing a degree to which a prediction generated by the relation is incorrect when compared to a given input-output pair provided in training data 1104. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of various possible variations of at least a supervised machine-learning process 1128 that may be used to determine relation between inputs and outputs. Supervised machine-learning processes may include classification algorithms as defined above.

Further referring to FIG. 11 , machine learning processes may include at least an unsupervised machine-learning processes 1132. An unsupervised machine-learning process, as used herein, is a process that derives inferences in datasets without regard to labels; as a result, an unsupervised machine-learning process may be free to discover any structure, relationship, and/or correlation provided in the data. Unsupervised processes may not require a response variable; unsupervised processes may be used to find interesting patterns and/or inferences between variables, to determine a degree of correlation between two or more variables, or the like.

Still referring to FIG. 11 , machine-learning module 1100 may be designed and configured to create a machine-learning model 1124 using techniques for development of linear regression models. Linear regression models may include ordinary least squares regression, which aims to minimize the square of the difference between predicted outcomes and actual outcomes according to an appropriate norm for measuring such a difference (e.g. a vector-space distance norm); coefficients of the resulting linear equation may be modified to improve minimization. Linear regression models may include ridge regression methods, where the function to be minimized includes the least-squares function plus term multiplying the square of each coefficient by a scalar amount to penalize large coefficients. Linear regression models may include least absolute shrinkage and selection operator (LASSO) models, in which ridge regression is combined with multiplying the least-squares term by a factor of 1 divided by double the number of samples. Linear regression models may include a multi-task lasso model wherein the norm applied in the least-squares term of the lasso model is the Frobenius norm amounting to the square root of the sum of squares of all terms. Linear regression models may include the elastic net model, a multi-task elastic net model, a least angle regression model, a LARS lasso model, an orthogonal matching pursuit model, a Bayesian regression model, a logistic regression model, a stochastic gradient descent model, a perceptron model, a passive aggressive algorithm, a robustness regression model, a Huber regression model, or any other suitable model that may occur to persons skilled in the art upon reviewing the entirety of this disclosure. Linear regression models may be generalized in an embodiment to polynomial regression models, whereby a polynomial equation (e.g. a quadratic, cubic or higher-order equation) providing a best predicted output/actual output fit is sought; similar methods to those described above may be applied to minimize error functions, as will be apparent to persons skilled in the art upon reviewing the entirety of this disclosure.

Continuing to refer to FIG. 11 , machine-learning algorithms may include, without limitation, linear discriminant analysis. Machine-learning algorithm may include quadratic discriminate analysis. Machine-learning algorithms may include kernel ridge regression. Machine-learning algorithms may include support vector machines, including without limitation support vector classification-based regression processes. Machine-learning algorithms may include stochastic gradient descent algorithms, including classification and regression algorithms based on stochastic gradient descent. Machine-learning algorithms may include nearest neighbors algorithms. Machine-learning algorithms may include various forms of latent space regularization such as variational regularization. Machine-learning algorithms may include Gaussian processes such as Gaussian Process Regression. Machine-learning algorithms may include cross-decomposition algorithms, including partial least squares and/or canonical correlation analysis. Machine-learning algorithms may include naïve Bayes methods. Machine-learning algorithms may include algorithms based on decision trees, such as decision tree classification or regression algorithms. Machine-learning algorithms may include ensemble methods such as bagging meta-estimator, forest of randomized tress, AdaBoost, gradient tree boosting, and/or voting classifier methods. Machine-learning algorithms may include neural net algorithms, including convolutional neural net processes.

It is to be noted that any one or more of the aspects and embodiments described herein may be conveniently implemented using one or more machines (e.g., one or more computing devices that are utilized as a user computing device for an electronic document, one or more server devices, such as a document server, etc.) programmed according to the teachings of the present specification, as will be apparent to those of ordinary skill in the computer art. Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those of ordinary skill in the software art. Aspects and implementations discussed above employing software and/or software modules may also include appropriate hardware for assisting in the implementation of the machine executable instructions of the software and/or software module.

Such software may be a computer program product that employs a machine-readable storage medium. A machine-readable storage medium may be any medium that is capable of storing and/or encoding a sequence of instructions for execution by a machine (e.g., a computing device) and that causes the machine to perform any one of the methodologies and/or embodiments described herein. Examples of a machine-readable storage medium include, but are not limited to, a magnetic disk, an optical disc (e.g., CD, CD-R, DVD, DVD-R, etc.), a magneto-optical disk, a read-only memory “ROM” device, a random-access memory “RAM” device, a magnetic card, an optical card, a solid-state memory device, an EPROM, an EEPROM, and any combinations thereof. A machine-readable medium, as used herein, is intended to include a single medium as well as a collection of physically separate media, such as, for example, a collection of compact discs or one or more hard disk drives in combination with a computer memory. As used herein, a machine-readable storage medium does not include transitory forms of signal transmission.

Such software may also include information (e.g., data) carried as a data signal on a data carrier, such as a carrier wave. For example, machine-executable information may be included as a data-carrying signal embodied in a data carrier in which the signal encodes a sequence of instruction, or portion thereof, for execution by a machine (e.g., a computing device) and any related information (e.g., data structures and data) that causes the machine to perform any one of the methodologies and/or embodiments described herein.

Examples of a computing device include, but are not limited to, an electronic book reading device, a computer workstation, a terminal computer, a server computer, a handheld device (e.g., a tablet computer, a smartphone, etc.), a web appliance, a network router, a network switch, a network bridge, any machine capable of executing a sequence of instructions that specify an action to be taken by that machine, and any combinations thereof. In one example, a computing device may include and/or be included in a kiosk.

FIG. 12 shows a diagrammatic representation of one embodiment of a computing device in the exemplary form of a computer system 1200 within which a set of instructions for causing a control system to perform any one or more of the aspects and/or methodologies of the present disclosure may be executed. It is also contemplated that multiple computing devices may be utilized to implement a specially configured set of instructions for causing one or more of the devices to perform any one or more of the aspects and/or methodologies of the present disclosure. Computer system 1200 includes a processor 1204 and a memory 1208 that communicate with each other, and with other components, via a bus 1212. Bus 1212 may include any of several types of bus structures including, but not limited to, a memory bus, a memory controller, a peripheral bus, a local bus, and any combinations thereof, using any of a variety of bus architectures.

Processor 1204 may include any suitable processor, such as without limitation a processor incorporating logical circuitry for performing arithmetic and logical operations, such as an arithmetic and logic unit (ALU), which may be regulated with a state machine and directed by operational inputs from memory and/or sensors; processor 1204 may be organized according to Von Neumann and/or Harvard architecture as a non-limiting example. Processor 1204 may include, incorporate, and/or be incorporated in, without limitation, a microcontroller, microprocessor, digital signal processor (DSP), Field Programmable Gate Array (FPGA), Complex Programmable Logic Device (CPLD), Graphical Processing Unit (GPU), general purpose GPU, Tensor Processing Unit (TPU), analog or mixed signal processor, Trusted Platform Module (TPM), a floating-point unit (FPU), and/or system on a chip (SoC).

Memory 1208 may include various components (e.g., machine-readable media) including, but not limited to, a random-access memory component, a read only component, and any combinations thereof. In one example, a basic input/output system 1216 (BIOS), including basic routines that help to transfer information between elements within computer system 1200, such as during start-up, may be stored in memory 1208. Memory 1208 may also include (e.g., stored on one or more machine-readable media) instructions (e.g., software) 1220 embodying any one or more of the aspects and/or methodologies of the present disclosure. In another example, memory 1208 may further include any number of program modules including, but not limited to, an operating system, one or more application programs, other program modules, program data, and any combinations thereof.

Computer system 1200 may also include a storage device 1224. Examples of a storage device (e.g., storage device 1224) include, but are not limited to, a hard disk drive, a magnetic disk drive, an optical disc drive in combination with an optical medium, a solid-state memory device, and any combinations thereof. Storage device 1224 may be connected to bus 1212 by an appropriate interface (not shown). Example interfaces include, but are not limited to, SCSI, advanced technology attachment (ATA), serial ATA, universal serial bus (USB), IEEE 1394 (FIREWIRE), and any combinations thereof. In one example, storage device 1224 (or one or more components thereof) may be removably interfaced with computer system 1200 (e.g., via an external port connector (not shown)). Particularly, storage device 1224 and an associated machine-readable medium 1228 may provide nonvolatile and/or volatile storage of machine-readable instructions, data structures, program modules, and/or other data for computer system 1200. In one example, software 1220 may reside, completely or partially, within machine-readable medium 1228. In another example, software 1220 may reside, completely or partially, within processor 1204.

Computer system 1200 may also include an input device 1232. In one example, a user of computer system 1200 may enter commands and/or other information into computer system 1200 via input device 1232. Examples of an input device 1232 include, but are not limited to, an alpha-numeric input device (e.g., a keyboard), a pointing device, a joystick, a gamepad, an audio input device (e.g., a microphone, a voice response system, etc.), a cursor control device (e.g., a mouse), a touchpad, an optical scanner, a video capture device (e.g., a still camera, a video camera), a touchscreen, and any combinations thereof. Input device 1232 may be interfaced to bus 1212 via any of a variety of interfaces (not shown) including, but not limited to, a serial interface, a parallel interface, a game port, a USB interface, a FIREWIRE interface, a direct interface to bus 1212, and any combinations thereof. Input device 1232 may include a touch screen interface that may be a part of or separate from display 1236, discussed further below. Input device 1232 may be utilized as a user selection device for selecting one or more graphical representations in a graphical interface as described above.

A user may also input commands and/or other information to computer system 1200 via storage device 1224 (e.g., a removable disk drive, a flash drive, etc.) and/or network interface device 1240. A network interface device, such as network interface device 1240, may be utilized for connecting computer system 1200 to one or more of a variety of networks, such as network 1244, and one or more remote devices 1248 connected thereto. Examples of a network interface device include, but are not limited to, a network interface card (e.g., a mobile network interface card, a LAN card), a modem, and any combination thereof. Examples of a network include, but are not limited to, a wide area network (e.g., the Internet, an enterprise network), a local area network (e.g., a network associated with an office, a building, a campus or other relatively small geographic space), a telephone network, a data network associated with a telephone/voice provider (e.g., a mobile communications provider data and/or voice network), a direct connection between two computing devices, and any combinations thereof. A network, such as network 1244, may employ a wired and/or a wireless mode of communication. In general, any network topology may be used. Information (e.g., data, software 1220, etc.) may be communicated to and/or from computer system 1200 via network interface device 1240.

Computer system 1200 may further include a video display adapter 1252 for communicating a displayable image to a display device, such as display device 1236. Examples of a display device include, but are not limited to, a liquid crystal display (LCD), a cathode ray tube (CRT), a plasma display, a light emitting diode (LED) display, and any combinations thereof. Display adapter 1252 and display device 1236 may be utilized in combination with processor 1204 to provide graphical representations of aspects of the present disclosure. In addition to a display device, computer system 1200 may include one or more other peripheral output devices including, but not limited to, an audio speaker, a printer, and any combinations thereof. Such peripheral output devices may be connected to bus 1212 via a peripheral interface 1256. Examples of a peripheral interface include, but are not limited to, a serial port, a USB connection, a FIREWIRE connection, a parallel connection, and any combinations thereof.

The foregoing has been a detailed description of illustrative embodiments of the invention. Various modifications and additions can be made without departing from the spirit and scope of this invention. Features of each of the various embodiments described above may be combined with features of other described embodiments as appropriate in order to provide a multiplicity of feature combinations in associated new embodiments. Furthermore, while the foregoing describes a number of separate embodiments, what has been described herein is merely illustrative of the application of the principles of the present invention. Additionally, although particular methods herein may be illustrated and/or described as being performed in a specific order, the ordering is highly variable within ordinary skill to achieve methods and systems according to the present disclosure. Accordingly, this description is meant to be taken only by way of example, and not to otherwise limit the scope of this invention.

Exemplary embodiments have been disclosed above and illustrated in the accompanying drawings. It will be understood by those skilled in the art that various changes, omissions and additions may be made to that which is specifically disclosed herein without departing from the spirit and scope of the present invention. 

What is claimed is:
 1. A system for transmitting and storing data based on a connection for a vehicle, the system comprising: a computing device, the computing device configured to: receive vehicle data; generate a vehicle collection datum as a function of the vehicle data, wherein generating the vehicle collection datum comprises mapping at least a n input datum from the vehicle data, to at least a torque datum; generate an expected vehicle model output as a function of a vehicle simulator and atleast a peak performance parameter; determine that the computing device is not currently connected to a network; start a timer using a timer module as a function of determining that the computing device is not currently connected to the network; generate a vehicle model output as a function of the vehicle simulator and the vehicle collection datum; store the vehicle collection datum, the expected vehicle model output and the vehicle model output in a recorder database once the timer has expired, wherein the recorder database is stored in the vehicle; communicatively connect the computing device to a second device as a function of a mesh network; authenticate the second device as a function of an authentication module; and communicate the vehicle collection datum, the expected vehicle model output and the vehicle model output to the second device as a function of the mesh network.
 2. The system of claim 1, wherein the vehicle further comprises an electric aircraft.
 3. The system of claim 1 further comprising a sensor communicatively connected to the computing device, the sensor configured to: detect a plurality of vehicle data; and transmit the plurality of vehicle data to the computing device.
 4. The system of claim 1, wherein the vehicle data further comprises: at least a sensor datum.
 5. The system of claim 1, wherein the authentication module is further configured to: receive a credential from the second device; compare the credential to an authorized credential stored within an authentication database; and authenticate the second device as a function of the comparison of the received credential from the second device and the authorized credential stored within the authentication database.
 6. The system of claim 1, wherein the computing device is further configured to determine a subset of received vehicle data from the vehicle collection datum to store, wherein the subset further comprises a plurality of vehicle model outputs.
 7. The system of claim 1, wherein the computing device is further configured to generate a machine-learning model, wherein the machine-learning model is configured to receive the vehicle data as an input and output the vehicle model output using a training set, wherein the training set contains a plurality of data entries including an element of a maneuver data correlated to an element of model data.
 8. The system of claim 1, wherein the computing device is further configured to: store the vehicle data in the recorder database; store the vehicle model output in the recorder database; and perform atleast a database encryption on each datum stored in the recorder database.
 9. The system of claim 1, wherein storing the vehicle collection datum in a recorder database once the timer has expired comprises closing all communication ports of the computing device, wherein the computing device comprises a plurality of communication ports.
 10. A method for transmitting and storing data based on a connection for a vehicle, the method comprising: receiving vehicle data; generating a vehicle collection datum as a function of the vehicle data, wherein generating the vehicle collection datum comprises mapping at least an input datum from the vehicle data, to at least a torque datum; generating an expected vehicle model output as a function of a vehicle simulator and at least a peak performance parameter; determining that a computing device is not currently connected to a network; starting a timer using a timer module as a function of determining that the computing device is not currently connected to the network; generating a vehicle model output as a function of the vehicle simulator and the vehicle collection datum; storing the vehicle collection datum, the expected vehicle model output and the vehicle model output in a recorder database once the timer has expired, wherein the recorder database is stored in the vehicle; communicatively connecting the computing device to a second device as a function of a mesh network; authenticating the second device as a function of an authentication module; and communicating the vehicle collection datum, the expected vehicle model output and the vehicle model output to the second device as a function of the mesh network.
 11. The method of claim 10, wherein the vehicle further comprises an electric aircraft.
 12. The method of claim 10 further comprising: detecting, by a sensor communicatively connected to the computing device the vehicle data; and transmitting the vehicle data to the computing device.
 13. The method of claim 10, wherein receiving the vehicle data further comprises receiving: at least a sensor datum.
 14. The method of claim 10, wherein authenticating the second device further comprises: receiving, by the authentication module, a credential from the second device; comparing the credential to an authorized credential stored within an authentication database; and authenticating the second device based on the comparison of the received credential from the second device to the authorized credential stored within the authentication database.
 15. The method of claim 10, wherein generating the vehicle collection datum further comprises determining a subset of received vehicle data from the vehicle collection datum to store, wherein the subset further comprises a plurality of vehicle model outputs.
 16. The method of claim 10, wherein generating the vehicle model output further comprises generating, by the computing device, a machine-learning model, wherein the machine-learning model is configured to receive the vehicle data as an input and output the vehicle model output as a function of a training data, wherein the training set contains a plurality of data entries including an element of a maneuver data correlated to an element of model data.
 17. The method of claim 10, the method further comprises: storing the vehicle data in the recorder database; storing the vehicle model output in the recorder database; and performing at least a database encryption on each datum stored in the recorder database.
 18. The method of claim 10, wherein storing the vehicle collection datum in a recorder database once the timer has expired comprises closing all communication ports of the computing device, wherein the computing device comprises a plurality of communication ports. 